Triple
T32184089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chokonen |
E822058
|
entity |
| Predicate | notableLeaderGroup |
P114666
|
FINISHED |
| Object | Cochise |
E1405524
|
NE 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: Cochise | Statement: [Chokonen, notableLeaderGroup, Cochise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLeaderGroup Context triple: [Chokonen, notableLeaderGroup, Cochise]
-
A.
notableLeaderInCommons
Indicates that a person is recognized as a prominent or distinguished leader within the House of Commons.
-
B.
notableLeaderAlias
Indicates that an alternative or commonly used name (alias) is associated with a notable leader.
-
C.
notableLeaderNationality
Indicates that the nationality specified is the country or nation with which a notable leader is officially or most prominently associated.
-
D.
notableLeaderSide
Indicates that a person is a prominent or distinguished leader associated with a particular side, faction, or party in a conflict or competition.
-
E.
notableLeaderFromTribe
chosen
Indicates that a person is recognized as a prominent or distinguished leader originating from a particular tribe.
- F. None of above.
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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f3b883b608190ad4224eab15e8528 |
completed | June 14, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:35 a.m.