Triple
T22293378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Myrōd |
E551054
|
entity |
| Predicate | languageContextOfName |
P15
|
FINISHED |
| Object | Middle Persian |
—
|
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: Middle Persian | Statement: [Lady Myrōd, languageContextOfName, Middle Persian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageContextOfName Context triple: [Lady Myrōd, languageContextOfName, Middle Persian]
-
A.
languageOfWorkOrName
chosen
Indicates the language in which a work is created or a name is expressed.
-
B.
languageFamilyContext
Indicates the broader linguistic family or grouping within which a particular language or linguistic element is situated.
-
C.
languageOfNamesake
Indicates the language in which the namesake of an entity (such as a person, place, or object) is named or expressed.
-
D.
nativeLanguageContext
Indicates the relationship in which a language functions as the primary or native linguistic context for an entity’s communication or interpretation.
-
E.
languageName
Indicates the specific name assigned to a language in the relationship.
- 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1560de3508190951ad0806ae3cc0d |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:41 p.m.