Triple
T36671027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation (EU) 2018/1726 |
E905416
|
entity |
| Predicate | definesHeadquartersOf |
P198429
|
FINISHED |
| Object | eu-LISA |
—
|
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: eu-LISA | Statement: [Regulation (EU) 2018/1726, definesHeadquartersOf, eu-LISA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesHeadquartersOf Context triple: [Regulation (EU) 2018/1726, definesHeadquartersOf, eu-LISA]
-
A.
hasHeadquartersFunctionFor
Indicates that an entity serves as the central coordinating or managing headquarters for another entity’s operations or activities.
-
B.
headquartersFor
Indicates that a location serves as the main administrative center or base of operations for an organization or entity.
-
C.
nearHeadquartersOf
Indicates that one entity is located geographically close to the headquarters of another entity.
-
D.
hasOrganizationHeadquarters
Indicates that an organization’s main administrative or operational center is located at a specific place.
-
E.
isBlockHeadquartersOf
Indicates that a particular block serves as the main headquarters location for a specified entity.
- 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
| PDg | Predicate description generation | batch_69fee25c7c548190a2c6e50074a33da4 |
completed | May 9, 2026, 7:29 a.m. |
Created at: May 3, 2026, 4:12 p.m.