Triple
T11237674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EVA Air |
E265984
|
entity |
| Predicate | operatesServiceScope |
P6851
|
FINISHED |
| Object | international routes |
—
|
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: international routes | Statement: [EVA Air, operatesServiceScope, international routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesServiceScope Context triple: [EVA Air, operatesServiceScope, international routes]
-
A.
operatesService
Indicates that an agent runs, manages, or provides a particular service.
-
B.
operationalScope
chosen
Indicates the range, extent, or boundaries within which an entity, process, or activity is authorized or designed to operate.
-
C.
operatesWithin
Indicates that one entity carries out its activities, functions, or operations inside the scope, boundaries, or jurisdiction defined by another entity.
-
D.
operatesServiceTo
Indicates that one entity runs or provides a transportation or service route to another entity or location.
-
E.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
- F. None of above.
Provenance (3 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e918375081908c2a7ccb50cbf331 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d7878906f48190b63ddc103a0c8f9b |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:30 p.m.