Triple
T31912122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Grand Tour |
E814714
|
entity |
| Predicate | chartPerformanceTerritory |
P4919
|
FINISHED |
| Object | United States |
—
|
NE NERFINISHED |
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: United States | Statement: [The Grand Tour, chartPerformanceTerritory, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chartPerformanceTerritory Context triple: [The Grand Tour, chartPerformanceTerritory, United States]
-
A.
chartPerformance
chosen
Indicates how well something ranks or behaves on a chart or leaderboard over a given period.
-
B.
performanceRegion
Indicates the geographic or market area within which a performance, operation, or activity takes place or is evaluated.
-
C.
overTerritory
Indicates that one entity has control, authority, or dominance over a specific territory or geographic area in relation to another.
-
D.
overseesTerritoryType
Indicates that an entity has supervisory or administrative responsibility over a specified type of territory.
-
E.
hubTerritory
Indicates that a given territory functions as a central hub or primary focal area within a broader geographic or organizational structure.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 12:01 a.m.