Triple
T1040490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ossetian language |
E22457
|
entity |
| Predicate | laterWrittenIn |
P23830
|
FINISHED |
| Object | Latin script |
—
|
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: Latin script | Statement: [Ossetian language, laterWrittenIn, Latin script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterWrittenIn Context triple: [Ossetian language, laterWrittenIn, Latin script]
-
A.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
B.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
-
C.
areWrittenOn
Indicates that one entity serves as a surface or medium on which another entity is inscribed, recorded, or written.
-
D.
writtenDuring
Indicates that the creation or authorship of something took place within a specified time period or historical event.
-
E.
likelyWrittenFrom
Indicates that something (such as a text, statement, or perspective) is probably authored or expressed from the viewpoint, context, or position of a particular entity.
- F. None of above. chosen
Provenance (4 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b845fa8c8190a7b69629883b62e2 |
completed | March 1, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69a4b72ba60881908b017ef3b2b9645e |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8444f708190815732408aa0463e |
completed | March 1, 2026, 10:05 p.m. |
Created at: March 1, 2026, 7:41 p.m.