Triple
T23629001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M. A. R. Barker |
E583552
|
entity |
| Predicate | settingLanguageCreated |
P56530
|
FINISHED |
| Object | Tsolyáni |
—
|
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: Tsolyáni | Statement: [M. A. R. Barker, settingLanguageCreated, Tsolyáni]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingLanguageCreated Context triple: [M. A. R. Barker, settingLanguageCreated, Tsolyáni]
-
A.
createdInLanguage
chosen
Indicates that something was produced, authored, or developed using a particular language (natural or programming).
-
B.
adoptedLanguage
Indicates that an entity has chosen and begun using a particular language, typically as its official, primary, or preferred means of communication.
-
C.
requiredLanguage
Indicates that a specific language is necessary or must be used for a given entity, action, or interaction.
-
D.
navigationLanguage
Indicates the language used for navigation-related content, such as menus, directions, or interface controls.
-
E.
targetLanguage
Indicates the language that is the intended recipient or focus of a communication, translation, or linguistic operation.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b1e5ae80819085c417e8d81b74ad |
completed | April 29, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:46 p.m.