Triple
T29887325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | provincial government of the Netherlands |
E759050
|
entity |
| Predicate | DutchTerm |
P13254
|
FINISHED |
| Object | provinciaal bestuur |
—
|
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: provinciaal bestuur | Statement: [provincial government of the Netherlands, DutchTerm, provinciaal bestuur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DutchTerm Context triple: [provincial government of the Netherlands, DutchTerm, provinciaal bestuur]
-
A.
cognateInDutch
Indicates that a word or term has a cognate (a historically related word with similar form and meaning) in the Dutch language.
-
B.
hasNameInDutch
chosen
Indicates that an entity is associated with a specific name or label expressed in the Dutch language.
-
C.
languageNameBe
Indicates that one entity is identified as the name of a language associated with another entity.
-
D.
hasLaterDutchName
Indicates that an entity was known by a different Dutch name at a later time than its original or earlier Dutch name.
-
E.
meaningInGerman
Indicates that one entity expresses the meaning or translation of another entity in the German language.
- 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_69f2245de2f48190a481404896b56254 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f676fdaee481908b38890b2e8aaf4b |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 6 p.m.