Triple
T28809402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South American airlines |
E727466
|
entity |
| Predicate | operate |
P198102
|
FINISHED |
| Object | passenger flights |
—
|
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: passenger flights | Statement: [South American airlines, operate, passenger flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operate Context triple: [South American airlines, operate, passenger flights]
-
A.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
-
B.
operation
Indicates that one entity performs, carries out, or controls the functioning of another entity or system.
-
C.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
D.
operations
Indicates that one entity performs, manages, or is responsible for the functional activities or processes of another entity.
-
E.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
| PDg | Predicate description generation | batch_69fecb4be24481908bda6197d7fc32f4 |
completed | May 9, 2026, 5:51 a.m. |
Created at: April 28, 2026, 6:30 a.m.