Triple
T29744615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ki-Adi-Mundi |
E752711
|
entity |
| Predicate | cloneCommander |
P167836
|
FINISHED |
| Object | Commander Bacara |
—
|
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: Commander Bacara | Statement: [Ki-Adi-Mundi, cloneCommander, Commander Bacara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cloneCommander Context triple: [Ki-Adi-Mundi, cloneCommander, Commander Bacara]
-
A.
parallelCommander
Indicates that two or more entities hold equivalent commander roles or authority in parallel, rather than in a strict superior–subordinate hierarchy.
-
B.
commanderAlias
Indicates that one commander is known or referred to by an alternative name, title, or identifier.
-
C.
coreCommand
Indicates that one entity serves as the primary or central command or control authority over another entity or process.
-
D.
componentCommand
Indicates that one entity issues or defines a command that is executed or interpreted by another component within a system.
-
E.
commander
Indicates that one entity holds authoritative military or organizational control over another entity or group.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 28, 2026, 7:50 p.m.