Triple
T29141680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RORS |
E738651
|
entity |
| Predicate | associatedWithRunwaysOf |
P105006
|
FINISHED |
| Object | Shimojishima Airport |
E201497
|
NE 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: Shimojishima Airport | Statement: [RORS, associatedWithRunwaysOf, Shimojishima Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRunwaysOf Context triple: [RORS, associatedWithRunwaysOf, Shimojishima Airport]
-
A.
associatedWithRunways
chosen
Indicates a relationship where something (such as an object, facility, or feature) is linked or connected to one or more runways.
-
B.
isRunwayOf
Indicates that a physical runway is a component or facility belonging to, used by, or officially associated with a particular airport or airfield.
-
C.
runwayAdjacentTo
Indicates that a runway is directly next to or alongside another feature or area, with no significant separation between them.
-
D.
hasRunwaysAt
Indicates that a location or facility possesses one or more runways situated at that place.
-
E.
hasRunwayAccessTo
Indicates that one location or facility is directly connected to another via a usable runway, allowing aircraft to move between them without leaving runway infrastructure.
- F. None of above.
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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a031045669c8190944781a48d09b5b6 |
completed | May 12, 2026, 11:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26614255188190afb4783d37ef628f |
completed | June 8, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_6a030fa775848190839b388f950d0364 |
completed | May 12, 2026, 11:31 a.m. |
Created at: April 28, 2026, 11:37 a.m.