Triple
T1114822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coming Home |
E11073
|
entity |
| Predicate | hasTrackPosition |
P13404
|
FINISHED |
| Object | track on the album Once Again |
—
|
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: track on the album Once Again | Statement: [Coming Home, hasTrackPosition, track on the album Once Again]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrackPosition Context triple: [Coming Home, hasTrackPosition, track on the album Once Again]
-
A.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
B.
positionInTrackList
chosen
Indicates the specific ordered place an item occupies within a track list.
-
C.
hasPositionOn
Indicates that one entity occupies or holds a specific role, job, or spatial location relative to another entity.
-
D.
playingPosition
Indicates the specific role or position an individual occupies while participating in a game or sport.
-
E.
tracksIndex
Indicates that one entity maintains or records the position, order, or index of another entity within a sequence or collection.
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bbd92a8c8190a16e55f3f739010f |
completed | March 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69a4bb42990c819080db96478fd4977e |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.