Triple
T32703208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BAC One-Eleven |
E836198
|
entity |
| Predicate | firstOperatorInUS |
P120239
|
FINISHED |
| Object | Mohawk Airlines |
E1491417
|
NE 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: Mohawk Airlines | Statement: [BAC One-Eleven, firstOperatorInUS, Mohawk Airlines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOperatorInUS Context triple: [BAC One-Eleven, firstOperatorInUS, Mohawk Airlines]
-
A.
initialOperator
chosen
Indicates that an entity serves as the first or primary operator initiating a process, action, or operation involving another entity.
-
B.
primaryOperator
Indicates that an entity serves as the main or leading operator responsible for performing or overseeing a specified operation or process in relation to another entity.
-
C.
USOperator
Indicates that an entity operates, manages, or provides services within the United States.
-
D.
firstRelayOperatedBy
Indicates that the first relay in a sequence or system is operated or controlled by a specified entity.
-
E.
primaryOperatorRank
Indicates the rank or level assigned to the main operator responsible for an action, process, or system.
- F. None of above.
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_69f3493323288190a4e88251035fe96e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34b154cef48190864a2561ae9e2bf4 |
completed | June 19, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:10 a.m.