Triple
T31271025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Three Brides |
E797384
|
entity |
| Predicate | titleLanguage_variant |
P115095
|
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: [The Three Brides, titleLanguage_variant, Dutch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleLanguage_variant Context triple: [The Three Brides, titleLanguage_variant, Dutch]
-
A.
labelLanguageVariant
chosen
Indicates that one label is a language-specific variant or localized form of another label.
-
B.
brandLanguageVariant
Indicates that one language variant of a brand is related to or derived from another language version of the same brand.
-
C.
languageVariant
Indicates that one language is a variant, dialect, or localized form of another language.
-
D.
linguisticVariant
Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
-
E.
officialLanguageVariant
Indicates that one language variety is an officially recognized form or version of another language within a specific jurisdiction or context.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
Created at: April 29, 2026, 9:13 p.m.