Triple
T525292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CDG |
E10902
|
entity |
| Predicate | hasRunwayConfiguration |
P15146
|
FINISHED |
| Object | multiple parallel runways |
—
|
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: multiple parallel runways | Statement: [CDG, hasRunwayConfiguration, multiple parallel runways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRunwayConfiguration Context triple: [CDG, hasRunwayConfiguration, multiple parallel runways]
-
A.
hasRunwayOrientation
Indicates that a runway is aligned or oriented in a specific directional heading.
-
B.
hasRunwayNumber
Indicates that an airport or airfield runway is assigned a specific identifying number.
-
C.
hasRunwayLighting
Indicates that a runway is equipped with lighting systems to aid visibility and operations, typically during low-light or night conditions.
-
D.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
E.
hasParallelRunway
Indicates that one runway is parallel in orientation and alignment to another runway.
- F. None of above. chosen
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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1b7f448819087e5e7f3b37d7142 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f0198ecc8190883849e5a8245963 |
completed | Feb. 28, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69a2f0dcff1881909c18e8c599c150a1 |
completed | Feb. 28, 2026, 1:42 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.