Triple
T16597481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enneüs Heerma |
E403246
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Heerma |
E403246
|
NE 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: Heerma | Statement: [Enneüs Heerma, familyName, Heerma]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heerma Context triple: [Enneüs Heerma, familyName, Heerma]
-
A.
Enneüs Heerma
chosen
Enneüs Heerma was a Dutch politician who served as a prominent leader of the Christian Democratic Appeal (CDA) and held several key government positions in the Netherlands.
-
B.
Jeetze
Jeetze is a river in northern Germany that flows through the town of Salzwedel in the state of Saxony-Anhalt.
-
C.
Legmeer
Legmeer is a residential neighborhood within the Dutch municipality of Uithoorn in the province of North Holland.
-
D.
Langeraar
Langeraar is a village in the Dutch province of South Holland, located within the municipality of Nieuwkoop.
-
E.
Schierke
Schierke is a small village in the Harz Mountains of Germany, known as a gateway to the Brocken peak and for its historic narrow-gauge railway connections and winter sports tourism.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d7367308190bf57b4a6a7bd33cc |
completed | April 18, 2026, 10:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0075a226788190bfad73ffb6b32ec4 |
completed | May 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 5:16 a.m.