Triple
T32902595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Dutchman |
E841650
|
entity |
| Predicate | languageOfWorkFeaturingCharacter |
P200786
|
FINISHED |
| Object | German |
—
|
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: German | Statement: [the Dutchman, languageOfWorkFeaturingCharacter, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfWorkFeaturingCharacter Context triple: [the Dutchman, languageOfWorkFeaturingCharacter, German]
-
A.
voicedInLanguage
Indicates that an entity produces spoken or vocal output using a specified language.
-
B.
languageOfKeyCharacter
chosen
Indicates the language spoken or used by a key character in a work or context.
-
C.
languageSpokenOnScreen
Indicates that a particular language is used in spoken dialogue or audible communication within an on-screen work (such as a film, show, or video).
-
D.
originalLanguageOfCharacterWork
Indicates that a language is the original language in which a particular character-related work (e.g., story, script, or media) was created or first expressed.
-
E.
currentlySpokenBy
Indicates that a language is presently being used as a spoken language by a person or group.
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fffbb5d0188190b6d168de8626ff68 |
completed | May 10, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69fffa3bc1208190a277961385a4789f |
completed | May 10, 2026, 3:23 a.m. |
Created at: May 1, 2026, 1:19 a.m.