Triple
T3768815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Tours |
E82745
|
entity |
| Predicate | includeFlatStages |
P16780
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Grand Tours, includeFlatStages, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeFlatStages Context triple: [Grand Tours, includeFlatStages, yes]
-
A.
flatStages
chosen
Indicates that the stages or phases of an event, process, or competition are flat, meaning they lack significant variation in difficulty, elevation, or complexity across stages.
-
B.
isFlat
Indicates that something has a level, even, or smooth surface without significant curves, bumps, or elevations.
-
C.
includedInLaterStageRevisions
Indicates that the subject is incorporated or carried forward into revised versions or stages that occur later in a process or workflow.
-
D.
numberOfStages
Indicates the total count of distinct stages or phases associated with a given process, event, or entity.
-
E.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc2d4b848190bf63fb3ed5d3b2d9 |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.