Triple
T10875386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Just One Love |
E256783
|
entity |
| Predicate | hasSequenceRelation |
P91161
|
FINISHED |
| Object | predecessor of Spirit |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: predecessor of Spirit | Statement: [Just One Love, hasSequenceRelation, predecessor of Spirit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSequenceRelation Context triple: [Just One Love, hasSequenceRelation, predecessor of Spirit]
-
A.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
B.
hasGenerationRelationship
Indicates that one entity is involved in producing, creating, or giving rise to another entity.
-
C.
hasPrimitiveRelation
Indicates a basic, direct relationship between entities that is not derived from or dependent on any other relations.
-
D.
hasChronologyRelation
chosen
Indicates a temporal ordering relationship between entities, specifying how one relates to another in time (e.g., before, after, or overlapping).
-
E.
hasPhaseRelation
Indicates that two entities are related by a specific phase difference or phase alignment in time or a cyclical process.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7518a1db08190abf0c524b81487fa |
completed | April 9, 2026, 7:13 a.m. |
| PD | Predicate disambiguation | batch_69d70d360c388190a3d829fe8862434f |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.