Triple
T630205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Can Change |
E15908
|
entity |
| Predicate | precedesInTrackList |
P11124
|
FINISHED |
| Object | next track on Get Lifted |
—
|
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: next track on Get Lifted | Statement: [I Can Change, precedesInTrackList, next track on Get Lifted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedesInTrackList Context triple: [I Can Change, precedesInTrackList, next track on Get Lifted]
-
A.
positionInTrackList
Indicates the specific ordered place an item occupies within a track list.
-
B.
appearsBefore
chosen
Indicates that one entity occurs, is positioned, or is presented earlier in an ordered sequence than another entity.
-
C.
predecessorInstrumentOf
Indicates that one instrument previously existed or was used in a role, function, or context that was later taken over or continued by another instrument.
-
D.
cededTo
Indicates that control, ownership, or authority over something was formally transferred from one entity to another.
-
E.
confersPrecedenceIn
Indicates that one entity is granted higher priority, rank, or standing over another within a specified context or domain.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ec051bc8190b3e3f8651a367d77 |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d01b29081908be87e4cd7726ff1 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.