Triple
T30279022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latvia–Estonia border |
E770033
|
entity |
| Predicate | governedByOrganization |
P33581
|
FINISHED |
| Object | European Union |
—
|
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: European Union | Statement: [Latvia–Estonia border, governedByOrganization, European Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedByOrganization Context triple: [Latvia–Estonia border, governedByOrganization, European Union]
-
A.
organizationTypeGoverned
Indicates that one entity governs or has authoritative control over a specific type or category of organization.
-
B.
hasOrganizationFor
Indicates that one entity possesses, is associated with, or is responsible for a particular organization in relation to some context or purpose.
-
C.
operatedByOrganization
Indicates that an activity, facility, or system is run, managed, or controlled by a specific organization.
-
D.
governedEntity
chosen
Indicates that one entity exercises authority, control, or governance over another entity.
-
E.
definesOrganizationOf
Indicates that one entity specifies or establishes the structural or functional organization of another entity.
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff70ecc1a481909571b18d56d982b8 |
completed | May 9, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69ff70322a3c8190837840ea42cd3093 |
completed | May 9, 2026, 5:34 p.m. |
Created at: April 29, 2026, 7:45 p.m.