Triple
T36918392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count von Krolock |
E913106
|
entity |
| Predicate | appearsInLanguageOfWork |
P118239
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Count von Krolock, appearsInLanguageOfWork, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInLanguageOfWork Context triple: [Count von Krolock, appearsInLanguageOfWork, English]
-
A.
usesWorkingLanguagesOf
Indicates that one entity employs or operates using the working languages associated with another entity.
-
B.
presentedInLanguage
Indicates that something (such as content, information, or a work) is expressed or made available using a particular language.
-
C.
isLanguageOf
Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
-
D.
languageOfUnderlyingWork
Indicates the language in which the original or underlying work (from which a derived or related work stems) is expressed.
-
E.
primaryLanguageInWork
chosen
Indicates that a specified language is the main or predominant language used within a particular work (such as a book, film, or document).
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
Created at: May 3, 2026, 4:13 p.m.