Triple
T26210891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ho people |
E655483
|
entity |
| Predicate | selfGoverningInstitution |
P26412
|
FINISHED |
| Object | Munda-Manki system |
—
|
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: Munda-Manki system | Statement: [Ho people, selfGoverningInstitution, Munda-Manki system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selfGoverningInstitution Context triple: [Ho people, selfGoverningInstitution, Munda-Manki system]
-
A.
selfGoverning
chosen
Indicates that an entity has the authority and capacity to govern, regulate, and manage itself independently, without external control.
-
B.
governedInstitution
Indicates that one entity exercises governing authority or administrative control over an institution.
-
C.
governsInstitution
Indicates that one entity holds authoritative control over, manages, or directs the operations and policies of an institution.
-
D.
governsInstitutionType
Indicates that an entity has authoritative control or regulatory oversight over a particular type or category of institution.
-
E.
establishedInstitution
Indicates that an entity founded, created, or formally set up an institution or organization.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d1706d481908ca3c7c39ba0d157 |
completed | May 2, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:52 p.m.