Triple
T2101611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turkic languages |
E37102
|
entity |
| Predicate | areSubjectOfDebate |
P15176
|
FINISHED |
| Object | Altaic hypothesis validity |
—
|
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: Altaic hypothesis validity | Statement: [Turkic languages, areSubjectOfDebate, Altaic hypothesis validity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areSubjectOfDebate Context triple: [Turkic languages, areSubjectOfDebate, Altaic hypothesis validity]
-
A.
hasLongTermDebateOn
chosen
Indicates that there is an ongoing, extended period of discussion, disagreement, or argument concerning a particular topic or issue.
-
B.
controversy
Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
-
C.
languageOfDebate
Indicates that a specified language is the one used for conducting a particular debate.
-
D.
debatedAsCauseOf
Indicates that one entity is discussed or argued over as a possible cause or origin of another entity.
-
E.
hasDebate
Indicates that there is a formal discussion or argument between entities, typically presenting opposing viewpoints on a topic.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbabc83a8819091f786f21d33b5a6 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b7b6288190afa11b4d93bd5666 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.