Triple
T6270002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Obsession |
E140506
|
entity |
| Predicate | trackNumberRelation |
P7270
|
FINISHED |
| Object | track on King of Stage |
—
|
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 King of Stage | Statement: [Love Obsession, trackNumberRelation, track on King of Stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackNumberRelation Context triple: [Love Obsession, trackNumberRelation, track on King of Stage]
-
A.
trackNumberOnAlbum
chosen
Indicates the specific position or sequence number that a track occupies on an album.
-
B.
tracksIndex
Indicates that one entity maintains or records the position, order, or index of another entity within a sequence or collection.
-
C.
trackPattern
Indicates that one entity follows, monitors, or records the behavior or state of another according to a defined pattern or sequence.
-
D.
trackType
Indicates the specific kind or category of track associated with an entity, such as its functional or physical classification.
-
E.
tracks
Indicates that one entity monitors, follows, or keeps a record of another entity’s state, behavior, or progress over 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_69c008cabc4081909723e2547c9d6cc0 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063a3f1d081908ccff88db94b1f9c |
completed | March 22, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69c05606fb50819082d1a5a91e5030b6 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:25 p.m.