Triple
T27336519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borssele |
E689965
|
entity |
| Predicate | inEuropeanUnion |
P10153
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Borssele, inEuropeanUnion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inEuropeanUnion Context triple: [Borssele, inEuropeanUnion, true]
-
A.
europeanUnionStatus
chosen
Indicates whether an entity is a member of, associated with, or otherwise holds a defined status in relation to the European Union.
-
B.
EuropeanAffiliation
Indicates that an entity is associated with Europe, such as by membership, origin, operation, or jurisdiction within European countries or institutions.
-
C.
useInEUInstitutions
Indicates that something is employed or applied within the official bodies or operations of European Union institutions.
-
D.
relationshipWithEU
Indicates the nature or status of an entity’s formal or informal relationship with the European Union.
-
E.
europeanRepresentation
Indicates that an entity serves as a representative or holds representational status for another entity within a European context (such as European institutions, markets, or jurisdictions).
- 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_69ef355e5b388190a8fc1eba9b4a6656 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f62acff3148190b836044eaadb1f9b |
completed | May 2, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:40 a.m.