Triple
T29543998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rohirric |
E749580
|
entity |
| Predicate | literarySubstituteLanguage |
P9828
|
FINISHED |
| Object | Old English |
—
|
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: Old English | Statement: [Rohirric, literarySubstituteLanguage, Old English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literarySubstituteLanguage Context triple: [Rohirric, literarySubstituteLanguage, Old English]
-
A.
textTranslation
Indicates a relationship where one text is rendered into another language or form while preserving its original meaning.
-
B.
literaryLanguage
chosen
Indicates that an entity is expressed, written, or communicated using a particular literary or standardized written language.
-
C.
verseLanguage
Indicates the language in which a verse is written or expressed.
-
D.
otherLanguage
Indicates that an entity has or uses an additional language distinct from its primary or main language.
-
E.
languageShift
Indicates a change in the primary language used by an entity, such as switching from one language to another over time or in a given context.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 28, 2026, 5:05 p.m.