Triple
T27162246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Association of European Airlines |
E682691
|
entity |
| Predicate | countryHeadquartered |
P93551
|
FINISHED |
| Object | Belgium |
—
|
NE NERFINISHED |
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: Belgium | Statement: [Association of European Airlines, countryHeadquartered, Belgium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryHeadquartered Context triple: [Association of European Airlines, countryHeadquartered, Belgium]
-
A.
continentHeadquarters
Indicates that an entity’s main headquarters is located on a specified continent.
-
B.
countryOfSeat
chosen
Indicates the country in which an organization’s official seat, headquarters, or principal office is located.
-
C.
hasOrganizationHeadquartered
Indicates that an organization has its main headquarters located in a specified place.
-
D.
hasOrganizationHeadquarters
Indicates that an organization’s main administrative or operational center is located at a specific place.
-
E.
governingBodyHeadquartersOf
Indicates that a location serves as the headquarters or main administrative center for a governing body or authority.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 27, 2026, 9:19 a.m.