Triple
T27574387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Around the World |
E699417
|
entity |
| Predicate | trackNumberOnBeHereNow |
P7270
|
FINISHED |
| Object | 6 |
—
|
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: 6 | Statement: [All Around the World, trackNumberOnBeHereNow, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackNumberOnBeHereNow Context triple: [All Around the World, trackNumberOnBeHereNow, 6]
-
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.
trackNumberWithinLine
Indicates the position or sequence number assigned to a track within a specific line or route.
-
D.
trackUsed
Indicates that a particular track (such as a route, path, or media track) has been utilized or selected in a given context.
-
E.
trackOver
Indicates that one entity follows, monitors, or records the behavior, state, or progress of another entity across a period of time or over a sequence of events.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 2:01 p.m.