Triple
T7570906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QQS |
E179234
|
entity |
| Predicate | associatedWithFacilityType |
P2836
|
FINISHED |
| Object | runway |
—
|
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: runway | Statement: [QQS, associatedWithFacilityType, runway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFacilityType Context triple: [QQS, associatedWithFacilityType, runway]
-
A.
hasFacilityType
chosen
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
B.
designedFacilityType
Indicates the type or category of facility that something (such as a plan, system, or component) is specifically designed for.
-
C.
basedOnFacility
Indicates that something is determined, derived, or decided according to the characteristics, rules, or conditions of a particular facility.
-
D.
anchorFacility
Indicates a facility that serves as the primary or reference location to which another facility, operation, or entity is functionally or organizationally tied.
-
E.
appliesToTransportFacilityType
Indicates that something is relevant or applicable specifically to a particular type or category of transport facility.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f920540c8190817712db5aa3eeff |
completed | March 27, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:51 p.m.