Triple
T32311617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaposia |
E825513
|
entity |
| Predicate | chiefResident |
P69264
|
FINISHED |
| Object | Little Crow III |
—
|
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: Little Crow III | Statement: [Kaposia, chiefResident, Little Crow III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chiefResident Context triple: [Kaposia, chiefResident, Little Crow III]
-
A.
chiefMedicalOfficer
Indicates that one entity serves as the highest-ranking medical authority or head of medical operations for the other entity.
-
B.
chief
chosen
Indicates that one entity holds the highest-ranking leadership or authoritative position over another entity or within a specified context.
-
C.
chiefAttendant
Indicates that one entity serves as the primary or leading attendant responsible for another entity.
-
D.
chiefLieutenantOf
Indicates that one person serves as the primary subordinate or top-ranking assistant to another leader or authority figure.
-
E.
chiefSurveyor
Indicates that one entity serves as the primary surveyor or head surveying official responsible for overseeing surveying activities for another entity.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bdb74c708190833b4c7d332b1a0d |
completed | May 3, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:46 a.m.