Triple
T28017074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marowijne |
E707573
|
entity |
| Predicate | languageVariantNameInDutch |
P13254
|
FINISHED |
| Object | Marowijne |
—
|
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: Marowijne | Statement: [Marowijne, languageVariantNameInDutch, Marowijne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageVariantNameInDutch Context triple: [Marowijne, languageVariantNameInDutch, Marowijne]
-
A.
hasNameInDutch
chosen
Indicates that an entity is associated with a specific name or label expressed in the Dutch language.
-
B.
languageVariant
Indicates that one language is a variant, dialect, or localized form of another language.
-
C.
linguisticVariant
Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
-
D.
officialLanguageVariant
Indicates that one language variety is an officially recognized form or version of another language within a specific jurisdiction or context.
-
E.
languageNameBe
Indicates that one entity is identified as the name of a language associated with another entity.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: April 27, 2026, 8:07 p.m.