Triple
T29744617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ki-Adi-Mundi |
E752711
|
entity |
| Predicate | councilColleague |
P68039
|
FINISHED |
| Object | Mace Windu |
—
|
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: Mace Windu | Statement: [Ki-Adi-Mundi, councilColleague, Mace Windu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: councilColleague Context triple: [Ki-Adi-Mundi, councilColleague, Mace Windu]
-
A.
associatedWithCouncil
Indicates that an entity has a formal or recognized connection, involvement, or affiliation with a council.
-
B.
cabinetColleague
Indicates that two individuals serve together as colleagues within the same governing cabinet.
-
C.
relationToCouncil
chosen
Indicates the nature or type of connection an entity has with a council, such as membership, oversight, affiliation, or governance relationship.
-
D.
chambersColleague
Indicates that two individuals work as colleagues within the same chamber, office, or professional setting.
-
E.
councilPartner
Indicates a formal collaborative relationship in which an entity serves as a partner within or to a council.
- 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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6736514d88190a856c8f0df03f022 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:50 p.m.