Triple
T2956744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Rally Championship |
E79948
|
entity |
| Predicate | typicalSurface |
P1242
|
FINISHED |
| Object | gravel |
—
|
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: gravel | Statement: [World Rally Championship, typicalSurface, gravel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSurface Context triple: [World Rally Championship, typicalSurface, gravel]
-
A.
surfaceType
chosen
Indicates the kind or classification of surface associated with an entity or interaction.
-
B.
typicalTexture
Indicates the usual or characteristic surface feel or consistency that is commonly associated with an entity.
-
C.
notableSurface
Indicates that one entity is a surface or exterior of particular significance or prominence in relation to another entity.
-
D.
typicalFinish
Indicates that an action, process, or event commonly or characteristically ends with a particular outcome or state.
-
E.
surfaceBehavior
Indicates how an entity behaves or interacts specifically at or on its surface.
- 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_69ad8b1276588190a374a0b12e0f7bdf |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad992998f08190ac9428310983172e |
completed | March 8, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69ad960c5c8881909d679912bd7d78f3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.