Triple
T23549376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cochise–Howard peace agreement |
E577993
|
entity |
| Predicate | indigenousLeaderInvolved |
P37571
|
FINISHED |
| Object | Cochise |
—
|
NE NERFINISHED |
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: Cochise | Statement: [Cochise–Howard peace agreement, indigenousLeaderInvolved, Cochise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indigenousLeaderInvolved Context triple: [Cochise–Howard peace agreement, indigenousLeaderInvolved, Cochise]
-
A.
politicalLeaderInvolved
Indicates that a political leader is actively involved in, associated with, or plays a significant role in a specified event, action, or situation.
-
B.
indigenousParticipants
Indicates that the participants are Indigenous people or groups, or are identified as belonging to Indigenous communities.
-
C.
indigenousGovernment
Indicates that a government is native to, and originates from, the original inhabitants of a particular region or territory.
-
D.
involvesLeader
chosen
Indicates that the relationship or action includes or is carried out by an entity serving in a leadership role.
-
E.
hasTribalLeadership
Indicates that an entity holds a leadership role or governing authority within a tribal group or community.
- 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aecd60a881908c257d9ba67080c8 |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:11 p.m.