Triple
T31250358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Howe Island–Sydney |
E796797
|
entity |
| Predicate | usesRunwaySurfaceTypeAtOrigin |
P422
|
FINISHED |
| Object | paved |
—
|
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: paved | Statement: [Lord Howe Island–Sydney, usesRunwaySurfaceTypeAtOrigin, paved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRunwaySurfaceTypeAtOrigin Context triple: [Lord Howe Island–Sydney, usesRunwaySurfaceTypeAtOrigin, paved]
-
A.
runwaySurface
chosen
Indicates the type or condition of the surface material that a runway is made of or covered with.
-
B.
hasRunwayOrigin
Indicates that something originates from, starts at, or is derived from a particular runway.
-
C.
hasRunwayType
Indicates that an airport or airfield has a runway of a specified type or surface classification.
-
D.
isRunwayOf
Indicates that a physical runway is a component or facility belonging to, used by, or officially associated with a particular airport or airfield.
-
E.
runwayCharacteristic
Indicates a relationship where specific attributes or features are associated with a runway.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 29, 2026, 9:11 p.m.