Triple
T9669508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolgan |
E233989
|
entity |
| Predicate | usesCaseSuffixes |
P23828
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Dolgan, usesCaseSuffixes, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCaseSuffixes Context triple: [Dolgan, usesCaseSuffixes, true]
-
A.
usedAsSuffixTo
Indicates that one entity functions as a suffix appended to another entity, typically to modify or extend its meaning.
-
B.
usesCaseHarmony
Indicates that one element selects or governs another element such that their grammatical cases are compatible or harmonized according to the language’s case system.
-
C.
usesCaseSystem
chosen
Indicates that one entity employs or operates using a particular case system (e.g., grammatical or structural case-marking system).
-
D.
hasCaseForms
Indicates that an entity possesses multiple grammatical case variants or inflected forms associated with it.
-
E.
usedWithSurname
Indicates that something (typically a given name or title) is used together with a particular surname in naming or reference.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c3d5b3481908c8c66a3528875aa |
completed | April 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.