Triple
T4593888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Rally Championship |
E103561
|
entity |
| Predicate | hasStageLocation |
P58188
|
FINISHED |
| Object | public roads closed for competition |
—
|
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: public roads closed for competition | Statement: [European Rally Championship, hasStageLocation, public roads closed for competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStageLocation Context triple: [European Rally Championship, hasStageLocation, public roads closed for competition]
-
A.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
B.
hasCheckInLocation
Indicates that an entity performs or is associated with a check-in action at a specific location.
-
C.
hasTemporalLocation
Indicates that something occurs, exists, or is valid during a specific time or time interval.
-
D.
hasShootingLocation
Indicates that an audiovisual work was filmed or recorded at a particular location.
-
E.
hasSatelliteLocation
Indicates that an entity has a secondary or remote location associated with it, such as a branch, satellite office, or auxiliary site.
- F. None of above. chosen
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_69bd43dccaf08190aa89e9991a289719 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd593e115081909b11149e02fe4ef3 |
completed | March 20, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:11 p.m.