Triple
T13134804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rue de la Science / Wetenschapsstraat |
E312054
|
entity |
| Predicate | languageOfDutchName |
P13254
|
FINISHED |
| Object | Dutch |
—
|
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: Dutch | Statement: [Rue de la Science / Wetenschapsstraat, languageOfDutchName, Dutch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfDutchName Context triple: [Rue de la Science / Wetenschapsstraat, languageOfDutchName, Dutch]
-
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.
hasNameInMiddleDutch
Indicates that an entity is associated with a specific name as it appears in the Middle Dutch language.
-
D.
hasDemonymLanguage
Indicates that a language is used as the demonym (people’s name or adjective of nationality) for inhabitants of a particular place or group.
-
E.
hasLanguageOfToponym
Indicates that a place name (toponym) is expressed in or associated with a particular 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981b3d72c8190b69ae56435a954fa |
completed | April 10, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69d9804543cc8190a23cd7da59a12a7b |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:08 p.m.