Triple
T35012905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rihad |
E1009977
|
entity |
| Predicate | inferredLanguage |
P155577
|
FINISHED |
| Object | Yoku-influenced Cyrodilic |
—
|
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: Yoku-influenced Cyrodilic | Statement: [Rihad, inferredLanguage, Yoku-influenced Cyrodilic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inferredLanguage Context triple: [Rihad, inferredLanguage, Yoku-influenced Cyrodilic]
-
A.
probableLanguageType
Indicates that something is likely to belong to, be expressed in, or be categorized under a particular language or type of language.
-
B.
recognizedLanguage
Indicates that an entity has identified, detected, or acknowledged a particular language as being used or present.
-
C.
primaryLanguageImplied
chosen
Indicates that an entity’s primary language is inferred or assumed rather than explicitly stated or directly observed.
-
D.
recognizesLanguages
Indicates that an entity has the ability to identify, understand, or acknowledge one or more languages.
-
E.
languageCategory
Indicates the classification relationship where a language is assigned to a particular linguistic or functional category.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.