Triple
T36638046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation (EU) No 1077/2011 |
E904512
|
entity |
| Predicate | establishesHeadquartersLocationForAgency |
P7525
|
FINISHED |
| Object | Tallinn |
—
|
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: Tallinn | Statement: [Regulation (EU) No 1077/2011, establishesHeadquartersLocationForAgency, Tallinn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishesHeadquartersLocationForAgency Context triple: [Regulation (EU) No 1077/2011, establishesHeadquartersLocationForAgency, Tallinn]
-
A.
establishesHeadquartersOf
chosen
Indicates that an entity selects and sets up the main administrative or operational center (headquarters) for another entity.
-
B.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
C.
headquartersSuccessorOrganizationLocation
Indicates that the location served as the headquarters for a successor organization that followed a previous entity.
-
D.
agencyLocatedIn
Indicates that an agency is situated or based within a specific geographic or administrative location.
-
E.
headquartersAt
Indicates that an organization’s main administrative center or primary office is located at a specified place.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: May 3, 2026, 4:11 p.m.