Triple
T26945818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doornhoek |
E678637
|
entity |
| Predicate | isLocatedInEuropeanUnion |
P150781
|
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: [Doornhoek, isLocatedInEuropeanUnion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInEuropeanUnion Context triple: [Doornhoek, isLocatedInEuropeanUnion, true]
-
A.
isInEuropeanUnionCountry
chosen
Indicates that the subject entity is located within, or belongs to, a country that is a member of the European Union.
-
B.
usesEuropeanUnionDSTRules
Indicates that the action or process is governed by, or conforms to, the European Union’s Digital Services Act (DSA) rules and requirements.
-
C.
legalStatusInEuropeanUnion
Indicates the legal status or standing that an entity holds within the jurisdictional framework of the European Union.
-
D.
locatedInEurozone
Indicates that the subject entity is situated within the geographic or economic area of the Eurozone.
-
E.
belongsToEURegionType
Indicates that an entity is classified within a specific type or category of European Union region.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 6:21 a.m.