Triple
T3768423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tour of Qatar |
E82736
|
entity |
| Predicate | typicalStageType |
P9638
|
FINISHED |
| Object | flat sprinters’ stages |
—
|
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: flat sprinters’ stages | Statement: [Tour of Qatar, typicalStageType, flat sprinters’ stages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStageType Context triple: [Tour of Qatar, typicalStageType, flat sprinters’ stages]
-
A.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
B.
typicalSegmentType
chosen
Indicates that something is classified as belonging to a usual or characteristic type of segment within a broader structure or sequence.
-
C.
thirdStageType
Indicates the specific kind or classification of a third stage within a multi-stage process or structure.
-
D.
firstStageType
Indicates that one entity is the type or category of the first stage or initial phase associated with another entity.
-
E.
stages
Indicates that one entity organizes, presents, or sets up another entity (such as an event, performance, or situation) to take place or be displayed.
- 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.