Triple
T23770745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OGZ |
E587518
|
entity |
| Predicate | usesRunwaySurfaceType |
P422
|
FINISHED |
| Object | Concrete |
—
|
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: Concrete | Statement: [OGZ, usesRunwaySurfaceType, Concrete]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRunwaySurfaceType Context triple: [OGZ, usesRunwaySurfaceType, Concrete]
-
A.
runwaySurface
chosen
Indicates the type or condition of the surface material that a runway is made of or covered with.
-
B.
hasRunwayType
Indicates that an airport or airfield has a runway of a specified type or surface classification.
-
C.
isRunwayOf
Indicates that a physical runway is a component or facility belonging to, used by, or officially associated with a particular airport or airfield.
-
D.
runwayCharacteristic
Indicates a relationship where specific attributes or features are associated with a runway.
-
E.
usesRunwayOf
Indicates that one entity makes use of the runway that belongs to or is associated with another entity.
- 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_69e2490d245881909028226a1393d624 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c465d7948190a4381e39f792a7b4 |
completed | April 29, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:15 p.m.