Triple
T35960338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayor of Nijmegen |
E1039976
|
entity |
| Predicate | DutchLabel |
P13254
|
FINISHED |
| Object | Burgemeester van Nijmegen |
—
|
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: Burgemeester van Nijmegen | Statement: [Mayor of Nijmegen, DutchLabel, Burgemeester van Nijmegen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DutchLabel Context triple: [Mayor of Nijmegen, DutchLabel, Burgemeester van Nijmegen]
-
A.
hasNameInDutch
chosen
Indicates that an entity is associated with a specific name or label expressed in the Dutch language.
-
B.
hasLaterDutchName
Indicates that an entity was known by a different Dutch name at a later time than its original or earlier Dutch name.
-
C.
hasDutchTitle
Indicates that an entity possesses a title or name expressed in the Dutch language.
-
D.
DutchSide
Indicates that one entity is located on, associated with, or belongs to the Dutch side of a border, region, or divided area in relation to another entity.
-
E.
certificationNetherlands
Indicates that an entity holds or is associated with a certification that is valid or recognized in the Netherlands.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.