Triple
T10909584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macro-Jibaroan |
E257658
|
entity |
| Predicate | basisOfProposal |
P23142
|
FINISHED |
| Object | possible cognate sets |
—
|
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: possible cognate sets | Statement: [Macro-Jibaroan, basisOfProposal, possible cognate sets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basisOfProposal Context triple: [Macro-Jibaroan, basisOfProposal, possible cognate sets]
-
A.
decisionBasis
chosen
Indicates the underlying reason, criterion, or rationale on which a decision is made.
-
B.
basisOfOrganization
Indicates that one entity serves as the foundational principle, criterion, or structure upon which another entity is organized or arranged.
-
C.
planningBasis
Indicates that one entity serves as the foundational reference or justification used by another entity when making plans or preparing actions.
-
D.
proposalType
Indicates the specific category or kind of proposal associated with an entity or event.
-
E.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77068e5488190bbc881ebf51d6b2e |
completed | April 9, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69d70d3d69e08190bb369e9a7927142c |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:22 p.m.