Triple
T15292372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VAL |
E365558
|
entity |
| Predicate | runningSurface |
P22809
|
FINISHED |
| Object | rubber tyres on concrete or steel |
—
|
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: rubber tyres on concrete or steel | Statement: [VAL, runningSurface, rubber tyres on concrete or steel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runningSurface Context triple: [VAL, runningSurface, rubber tyres on concrete or steel]
-
A.
runningTerrain
chosen
Indicates the type of ground or surface on which the running activity takes place.
-
B.
runwaySurface
Indicates the type or condition of the surface material that a runway is made of or covered with.
-
C.
hasRaceSurface
Indicates that an event or activity takes place on, or is associated with, a specific type of race surface.
-
D.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
E.
runningDiscipline
Indicates a relationship where an entity participates in or is associated with running as a sport or athletic discipline.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03680b60c8190a3ea54a9d34c8105 |
completed | April 16, 2026, 1:08 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:15 a.m.