Triple
T3458349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Norse morphology |
E72960
|
entity |
| Predicate | usesInflectionFor |
P3088
|
FINISHED |
| Object | case marking |
—
|
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: case marking | Statement: [Old Norse morphology, usesInflectionFor, case marking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInflectionFor Context triple: [Old Norse morphology, usesInflectionFor, case marking]
-
A.
hasCaseInflection
chosen
Indicates that a word or phrase changes form to reflect grammatical case (such as nominative, accusative, etc.) in a given language context.
-
B.
inflectionOf
Indicates that one linguistic form is an inflected variant of another base or lemma form.
-
C.
usesNamingSystem
Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
-
D.
usesAlphabet
Indicates that one entity employs or is written using the alphabet or writing system associated with another entity.
-
E.
usedAsSuffixTo
Indicates that one entity functions as a suffix appended to another entity, typically to modify or extend its meaning.
- 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbae36e748190bf20fd3c6de22e19 |
completed | March 8, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69adae041d588190a84a02bca94adec8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.