Triple
T6203209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorothy Stanbury |
E138685
|
entity |
| Predicate | languageOfWorkWhereAppears |
P15
|
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: [Dorothy Stanbury, languageOfWorkWhereAppears, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfWorkWhereAppears Context triple: [Dorothy Stanbury, languageOfWorkWhereAppears, English]
-
A.
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).
-
B.
languageOfParentWork
Indicates that the specified language is the language in which the parent (original or containing) work is expressed.
-
C.
languageOfWorkOrName
chosen
Indicates the language in which a work is created or a name is expressed.
-
D.
languageOfWritings
Indicates that a specified language is the one in which certain writings or written works are composed.
-
E.
languageOfExpression
Indicates that a particular language is used as the medium or form in which an expression (such as a text, utterance, or work) is realized.
- 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0626a32908190a3332008aee2e4a9 |
completed | March 22, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.