Triple
T27454711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 3L |
E692554
|
entity |
| Predicate | hasSafetyArea |
P60338
|
FINISHED |
| Object | runway safety area (RSA) as required by regulation |
—
|
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 safety area (RSA) as required by regulation | Statement: [Runway 3L, hasSafetyArea, runway safety area (RSA) as required by regulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSafetyArea Context triple: [Runway 3L, hasSafetyArea, runway safety area (RSA) as required by regulation]
-
A.
hasSecurityArea
Indicates that an entity is associated with, assigned to, or falls within a defined security-controlled area or zone.
-
B.
safeArea
chosen
Indicates that a specified region or zone is designated as protected or free from danger, harm, or threats.
-
C.
hasProtectedArea
Indicates that an entity possesses, includes, or is associated with a designated protected area for conservation or restricted use.
-
D.
hasProtectedAreaCoverage
Indicates that a specified portion or extent of an area falls within officially designated protected areas.
-
E.
hasSafetyCharacteristic
Indicates that an entity possesses a specific safety-related property, feature, or attribute.
- 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 12:48 p.m.