Triple
T10778484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dené–Caucasian |
E254255
|
entity |
| Predicate | relatedHypothesis |
P38188
|
FINISHED |
| Object | Sino-Caucasian hypothesis |
—
|
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: Sino-Caucasian hypothesis | Statement: [Dené–Caucasian, relatedHypothesis, Sino-Caucasian hypothesis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedHypothesis Context triple: [Dené–Caucasian, relatedHypothesis, Sino-Caucasian hypothesis]
-
A.
relatedBelief
Indicates that one belief is connected to, derived from, or otherwise associated with another belief in some meaningful way.
-
B.
moreCloselyRelatedTo
Indicates that one entity has a stronger or closer relationship, connection, or similarity to a second entity than to some other reference entity.
-
C.
relatedConjecture
chosen
Indicates that one conjecture is connected or associated with another conjecture, such as by similarity, dependency, or thematic relation.
-
D.
relatedTest
Indicates that there exists some form of connection or association between one test and another.
-
E.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732c25478819093dedec0c8556777 |
completed | April 9, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69d6f31455648190b5c24690487b1b54 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.