Triple
T18963037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bunge la Tanzania |
E463956
|
entity |
| Predicate | roleInUnion |
P11005
|
FINISHED |
| Object | legislature for the Union Government of Tanzania |
—
|
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: legislature for the Union Government of Tanzania | Statement: [Bunge la Tanzania, roleInUnion, legislature for the Union Government of Tanzania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInUnion Context triple: [Bunge la Tanzania, roleInUnion, legislature for the Union Government of Tanzania]
-
A.
allianceRole
Indicates the specific function, status, or responsibility an entity holds within an alliance or cooperative partnership.
-
B.
memberUnion
Indicates that an entity is a member (part of) a specified union or collective group.
-
C.
roleInFederalism
Indicates the specific function, authority, or responsibility an entity holds within a federal system of divided and shared governance.
-
D.
roleInCouncil
chosen
Indicates that an entity holds a specific position or function within a council or governing body.
-
E.
roleInRepublic
Indicates that an entity holds or plays a specific role or function within a republic or republican system.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5d420f481909aa22a0d22ac4af1 |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon