Triple
T24660697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uralists |
E610529
|
entity |
| Predicate | languageFamilyOfInterest |
P35117
|
FINISHED |
| Object | Uralic language family |
—
|
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: Uralic language family | Statement: [Uralists, languageFamilyOfInterest, Uralic language family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageFamilyOfInterest Context triple: [Uralists, languageFamilyOfInterest, Uralic language family]
-
A.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
-
B.
languageFamilyOf
chosen
Indicates that one entity is the language family to which the other entity (a specific language) belongs.
-
C.
languageFamilyConcerned
Indicates that something is related to, involves, or pertains to a particular language family.
-
D.
languageFamilyContext
Indicates the broader linguistic family or grouping within which a particular language or linguistic element is situated.
-
E.
languageFamilyUsedFor
Indicates that a particular language family is employed or utilized for a specific purpose, context, or function.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 2:34 a.m.