Triple
T28024564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shining |
E707777
|
entity |
| Predicate | followsInSingleChronologyOf |
P104670
|
FINISHED |
| Object | previous single before I'm the One |
—
|
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: previous single before I'm the One | Statement: [Shining, followsInSingleChronologyOf, previous single before I'm the One]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsInSingleChronologyOf Context triple: [Shining, followsInSingleChronologyOf, previous single before I'm the One]
-
A.
followsInReleaseChronology
chosen
Indicates that one entity is released after another in a chronological sequence of releases.
-
B.
chronologyPrecedes
Indicates that one event or state occurs earlier in time than another in a chronological sequence.
-
C.
chronologicallyAfter
Indicates that one event or state occurs later in time than another.
-
D.
hasChronologyRelation
Indicates a temporal ordering relationship between entities, specifying how one relates to another in time (e.g., before, after, or overlapping).
-
E.
chronologicallyOrdered
Indicates that the related entities are arranged in the order in which they occur in time.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 27, 2026, 8:12 p.m.