Triple
T27546742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ara Zobayan |
E695382
|
entity |
| Predicate | cooperatedWithATC |
P163280
|
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: [Ara Zobayan, cooperatedWithATC, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cooperatedWithATC Context triple: [Ara Zobayan, cooperatedWithATC, yes]
-
A.
appliesToAirspaceOf
Indicates that a rule, restriction, or condition is specifically relevant to, or in effect within, a particular airspace.
-
B.
providesATCServiceTo
Indicates that one entity delivers air traffic control services or support to another entity.
-
C.
airTrafficRole
Indicates the specific function or responsibility an entity has within the context of air traffic operations or control.
-
D.
hasControlledAirspace
Indicates that a specified location or region falls within airspace where aircraft operations are regulated and managed by an aviation authority.
-
E.
usedInAirTrafficControlFor
Indicates that something serves as a tool, system, or resource specifically employed in the management, monitoring, or regulation of air traffic.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6369a22688190a5674191c90a5d12 |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 1:33 p.m.