Triple
T34220222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proto-Mari |
E877902
|
entity |
| Predicate | lexiconSharesOriginWith |
P28322
|
FINISHED |
| Object | other Uralic branches |
—
|
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: other Uralic branches | Statement: [Proto-Mari, lexiconSharesOriginWith, other Uralic branches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lexiconSharesOriginWith Context triple: [Proto-Mari, lexiconSharesOriginWith, other Uralic branches]
-
A.
sharesLexiconWith
Indicates that two entities use or are associated with the same set of lexical items, vocabulary, or word inventory.
-
B.
sharesEtymologyWith
chosen
Indicates that two terms originate from the same linguistic root or source word, or have closely related historical word origins.
-
C.
sharesTermWith
Indicates that two entities are associated with or contain at least one common term (e.g., word, label, or keyword) in their representations.
-
D.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
E.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71081727c819096d2462bf0fd4b26 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.