Triple
T5094396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ælfric’s Grammar |
E114830
|
entity |
| Predicate | usesVernacular |
P18209
|
FINISHED |
| Object | Old English |
—
|
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: Old English | Statement: [Ælfric’s Grammar, usesVernacular, Old English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVernacular Context triple: [Ælfric’s Grammar, usesVernacular, Old English]
-
A.
linguisticVariant
Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
-
B.
usesColloquialCharacters
Indicates that an expression, name, or text is written using informal, non-standard, or colloquial characters rather than formal or standard script.
-
C.
hasColloquialVariety
Indicates that one linguistic form, expression, or variety is an informal, colloquial counterpart or version of another.
-
D.
languageUse
chosen
Indicates the language or languages an entity uses for communication, expression, or interaction.
-
E.
languageVariant
Indicates that one language is a variant, dialect, or localized form of another language.
- 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7563ad608190879a26a0bf07c3f6 |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715c0a448190afc837c6c31dc6ab |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.