Triple
T27394757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buysscheure |
E691645
|
entity |
| Predicate | localNameInWestFlemish |
P13254
|
FINISHED |
| Object | Buisscheure |
—
|
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: Buisscheure | Statement: [Buysscheure, localNameInWestFlemish, Buisscheure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localNameInWestFlemish Context triple: [Buysscheure, localNameInWestFlemish, Buisscheure]
-
A.
WestFrisianName
Indicates that the associated name is the form used in the West Frisian language for the given entity.
-
B.
hasNameInWalloon
Indicates that an entity is associated with a specific name expressed in the Walloon language.
-
C.
languageNameBe
Indicates that one entity is identified as the name of a language associated with another entity.
-
D.
hasNameInBelgium
Indicates that an entity is known or referred to by a particular name specifically within the context of Belgium.
-
E.
hasNameInDutch
chosen
Indicates that an entity is associated with a specific name or label expressed in the Dutch 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 12:27 p.m.