Triple
T18621531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 06L/24R |
E455161
|
entity |
| Predicate | hasReciprocalRightDesignation |
P132436
|
FINISHED |
| Object | R |
—
|
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: R | Statement: [Runway 06L/24R, hasReciprocalRightDesignation, R]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReciprocalRightDesignation Context triple: [Runway 06L/24R, hasReciprocalRightDesignation, R]
-
A.
isDesignatedRight
Indicates that something has been formally assigned or recognized as the correct or official right in a given context.
-
B.
bilateralRelation
Indicates a mutual or two-way relationship between two entities, where each affects or interacts with the other.
-
C.
mutualRecognitionBetween
Indicates that two or more entities acknowledge and recognize each other in a reciprocal manner.
-
D.
hasTreatyRight
Indicates that an entity holds a legally recognized right or entitlement established by a formal treaty with another party.
-
E.
hasExecutiveCounterpart
Indicates that one entity serves as the executive-level counterpart or equivalent to another entity within an organizational or governance structure.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54f0146f48190a872032db6e660c6 |
completed | April 19, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e485f5d1588190b44f31cbc54c0a9d |
completed | April 19, 2026, 7:36 a.m. |
Created at: April 10, 2026, 11:46 a.m.