Triple
T36251834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cahuapanan–Jivaroan hypothesis |
E891822
|
entity |
| Predicate | isWidelyAccepted |
P184812
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Cahuapanan–Jivaroan hypothesis, isWidelyAccepted, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWidelyAccepted Context triple: [Cahuapanan–Jivaroan hypothesis, isWidelyAccepted, false]
-
A.
isWidelyUsed
Indicates that something is commonly or extensively utilized across many contexts, users, or situations.
-
B.
isWidelyPerformed
Indicates that an action or behavior is carried out by a large number of individuals or groups across many contexts or locations.
-
C.
isWidelyAvailable
Indicates that something can be easily obtained or accessed by many people across numerous locations or channels.
-
D.
isWidelyFollowedBy
Indicates that one entity is followed, subscribed to, or tracked by a large number of other entities.
-
E.
alsoAcceptedIn
Indicates that something is additionally recognized, approved, or valid within another context, system, or location beyond its primary one.
- F. None of above. chosen
Provenance (4 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5fab9908190aaecb5e3c6dd1f9f |
completed | May 3, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b57aa0848190a22c31c3ff90e0ab |
completed | May 3, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:09 p.m.