Triple
T13426376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rally Catalunya |
E313491
|
entity |
| Predicate | previousSurfaceConfiguration |
P51587
|
FINISHED |
| Object | all-tarmac rally |
—
|
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: all-tarmac rally | Statement: [Rally Catalunya, previousSurfaceConfiguration, all-tarmac rally]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousSurfaceConfiguration Context triple: [Rally Catalunya, previousSurfaceConfiguration, all-tarmac rally]
-
A.
formerSurface
Indicates that one entity previously served as the surface or outer layer of another entity, but no longer does so.
-
B.
previousConfigurationLocation
Indicates the location where an entity’s earlier or prior configuration was stored or situated.
-
C.
targetSurface
Indicates the surface or area that an action, effect, or object is directed at or intended to impact.
-
D.
previousMode
Indicates that one mode directly precedes another in a sequence or state transition.
-
E.
formerlyConfiguration
chosen
Indicates that one entity was previously configured or arranged in the state or setup represented by the other entity, but is no longer so.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed1f9208190bf5ef5b8a7ded376 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.