Triple
T32079941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | deelgemeente |
E819265
|
entity |
| Predicate | hasTranslationInEnglish |
P43395
|
FINISHED |
| Object | sub-municipality |
—
|
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: sub-municipality | Statement: [deelgemeente, hasTranslationInEnglish, sub-municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTranslationInEnglish Context triple: [deelgemeente, hasTranslationInEnglish, sub-municipality]
-
A.
hasTranslation
Indicates that one entity is a translation or translated version of another entity in a different language.
-
B.
hasTranslated
Indicates that one entity has rendered the content of another entity from one language into a different language.
-
C.
hasWorkTranslatedInto
Indicates that a work has been translated into a specified language or target work.
-
D.
hasEnglishEdition
chosen
Indicates that one entity has a version or edition of itself that is produced or available in the English language.
-
E.
hasTranslatedMeaning
Indicates that one entity expresses the meaning of another entity in a different language through translation.
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fee691952c8190822da83e46311d1d |
completed | May 9, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69fee62f285c8190a625562a9b80526e |
completed | May 9, 2026, 7:45 a.m. |
Created at: May 1, 2026, 12:24 a.m.