Triple
T3155733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris–Los Angeles |
E65980
|
entity |
| Predicate | requiresETOPS |
P46660
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Paris–Los Angeles, requiresETOPS, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresETOPS Context triple: [Paris–Los Angeles, requiresETOPS, yes]
-
A.
requiresForVFR
Indicates that one entity must be present, satisfied, or fulfilled as a prerequisite for another entity to operate or be valid under Visual Flight Rules (VFR).
-
B.
usedByAircraftType
Indicates that something (such as equipment, infrastructure, or a procedure) is employed or operated by a specific type or category of aircraft.
-
C.
appliesToAirspaceOf
Indicates that a rule, restriction, or condition is specifically relevant to, or in effect within, a particular airspace.
-
D.
requiresTransponder
Indicates that one entity must have or use a transponder in order to interact with, access, or be accepted by another entity or system.
-
E.
hasInstrumentApproach
Indicates that an approach procedure to a location or runway is conducted using specified navigation instruments or instrument-based methods.
- 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_69ad8584485081909ed529e890cadc4a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5e97548819084643586fff2e3cb |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfbf0348190952a6bca8fc5fed1 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada1e4f7288190a80a1672e458132d |
completed | March 8, 2026, 4:20 p.m. |
Created at: March 8, 2026, 3:05 p.m.