Triple
T32232444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rama |
E823376
|
entity |
| Predicate | hasPrimaryGoverningBodyType |
P2886
|
FINISHED |
| Object | band council |
—
|
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: band council | Statement: [Rama, hasPrimaryGoverningBodyType, band council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryGoverningBodyType Context triple: [Rama, hasPrimaryGoverningBodyType, band council]
-
A.
hasMainGoverningBody
chosen
Indicates that an entity possesses a primary official organization or authority responsible for its overall governance or decision-making.
-
B.
governingBodyOfType
Indicates that an entity serves as the official governing body for another entity of a specified type or category.
-
C.
hasGovernmentalBodyType
Indicates the specific kind or classification of governmental body that an entity possesses or is associated with.
-
D.
governingBodyStatus
Indicates the official condition, standing, or operational state of a governing body in relation to its authority or function.
-
E.
governingBodyIncludes
Indicates that a governing body has a particular entity as one of its members or constituent parts.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00b479c1588190af6e0698b7f8d7f7 |
completed | May 10, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_6a00b4158260819087d0cfad8b18cef4 |
completed | May 10, 2026, 4:36 p.m. |
Created at: May 1, 2026, 12:39 a.m.