Triple
T20876414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Got to Get You into My Life |
E514027
|
entity |
| Predicate | trackNumberOnRevolverUK |
P7270
|
FINISHED |
| Object | 13 |
—
|
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: 13 | Statement: [Got to Get You into My Life, trackNumberOnRevolverUK, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackNumberOnRevolverUK Context triple: [Got to Get You into My Life, trackNumberOnRevolverUK, 13]
-
A.
trackNumberOnAlbum
chosen
Indicates the specific position or sequence number that a track occupies on an album.
-
B.
ringNumber
Indicates that an entity is assigned a specific ring identifier or position number within a ring-structured system or sequence.
-
C.
isTrackNumberUnknown
Indicates that the track number associated with an item or entity is not known or has not been specified.
-
D.
trackNumberOnJustice
Indicates the position or sequence number that something occupies on the entity referred to as "Justice," such as a track on an album.
-
E.
trackNumberOnPhrenology
Indicates that a specific track or item is assigned a particular sequence number within the context of phrenology-related content or data.
- 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c674f68c8190a7b43aeea5b9b976 |
completed | April 21, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:45 p.m.