Triple
T34522057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Caucasian |
E886304
|
entity |
| Predicate | macroFamilyHypothesisName |
P138721
|
FINISHED |
| Object | Dene–Caucasian |
—
|
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: Dene–Caucasian | Statement: [North Caucasian, macroFamilyHypothesisName, Dene–Caucasian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: macroFamilyHypothesisName Context triple: [North Caucasian, macroFamilyHypothesisName, Dene–Caucasian]
-
A.
macroFamily
Indicates that two or more language families are hypothesized to share a common higher-level genetic origin, forming a larger proposed macro-family grouping.
-
B.
languageFamilyHypotheses
chosen
Indicates proposed or theorized genealogical relationships among languages, grouping them into potential common families or macro-families.
-
C.
belongsToMacrofamily
Indicates that a language is classified as part of a larger proposed language macrofamily.
-
D.
namedForFamily
Indicates that one entity is named in honor of, or derived from the name of, a particular family or family group.
-
E.
macroFamilySize
Indicates the total number of distinct families or family-level groupings contained within a larger macro-level family or classification.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:02 a.m.