Triple
T9573153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COPA |
E230976
|
entity |
| Predicate | usedByAirlineRole |
P89878
|
FINISHED |
| Object | flag carrier of Panama |
—
|
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: flag carrier of Panama | Statement: [COPA, usedByAirlineRole, flag carrier of Panama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByAirlineRole Context triple: [COPA, usedByAirlineRole, flag carrier of Panama]
-
A.
airportLineRole
Indicates the specific functional role or responsibility an entity has in relation to an airport transit line or route.
-
B.
usedOnAircraftRole
Indicates that something is employed or applied in the context of a specific role or function on an aircraft.
-
C.
referredAircraftRole
Indicates that one aircraft is mentioned or designated in relation to another aircraft’s role, function, or status within a specific context or event.
-
D.
airlinesUse
Indicates that certain airlines operate, employ, or make use of a specified resource, service, or system.
-
E.
servesAirlineType
Indicates that a service provider (such as an airport, terminal, or facility) accommodates or operates flights for a specified type or category of airline.
- 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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd998d79cc8190b94e5953915a5fa4 |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:04 p.m.