Triple
T33812889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On the Run II Tour |
E866586
|
entity |
| Predicate | featuresDuoName |
P199103
|
FINISHED |
| Object | The Carters |
E1228682
|
NE 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: The Carters | Statement: [On the Run II Tour, featuresDuoName, The Carters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresDuoName Context triple: [On the Run II Tour, featuresDuoName, The Carters]
-
A.
featuresProductionDuo
Indicates that an entity includes or prominently involves a specific production duo in its creation or presentation.
-
B.
featuresDoubleAct
chosen
Indicates that an entity includes or presents a performance, show, or act involving two main performers acting together as a pair.
-
C.
featuresDualRole
Indicates that an entity simultaneously fulfills two distinct roles or functions within a given context.
-
D.
featuresDuetPartner
Indicates that an entity (such as a song or performance) includes another entity as a duet partner participating jointly in the performance.
-
E.
dualSIMVariantName
Indicates the specific name or label assigned to a particular dual-SIM variant of a device or product.
- F. None of above.
Provenance (4 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0224f4b6cc8190a8f79700a9af765f |
completed | May 11, 2026, 6:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a366e992b708190829c9b81a46ce86b |
completed | June 20, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_6a0223f01eb081909419518fdd45f2a4 |
completed | May 11, 2026, 6:46 p.m. |
Created at: May 1, 2026, 1:46 a.m.