Triple
T38221929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transeurasian hypothesis |
E1012033
|
entity |
| Predicate | hasSubproposal |
P201662
|
FINISHED |
| Object | Micro-Altaic 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: Micro-Altaic hypothesis | Statement: [Transeurasian hypothesis, hasSubproposal, Micro-Altaic hypothesis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubproposal Context triple: [Transeurasian hypothesis, hasSubproposal, Micro-Altaic hypothesis]
-
A.
hasSubproposals
chosen
Indicates that an item or proposal includes one or more subordinate or component proposals associated with it.
-
B.
hasProposal
Indicates that an entity possesses, is associated with, or is the subject of a specific proposal.
-
C.
hasProposed
Indicates that one entity has formally suggested or put forward something (such as an idea, plan, or offer) to another entity for consideration or acceptance.
-
D.
hasSubsummit
Indicates that one entity holds a subordinate or lower-ranked position under another entity within a hierarchical structure.
-
E.
isProposed
Indicates that an entity has been formally suggested or put forward for consideration, approval, or adoption.
- 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a007dd341108190a1d03eab46041694 |
completed | May 10, 2026, 12:45 p.m. |
| PD | Predicate disambiguation | batch_6a007b1fe2a881909ec50a1e65e4651b |
completed | May 10, 2026, 12:33 p.m. |
Created at: May 3, 2026, 4:30 p.m.