Triple
T30228973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandalorian Wars |
E768570
|
entity |
| Predicate | commandedByOnRepublicSide |
P1407
|
FINISHED |
| Object | Revan |
—
|
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: Revan | Statement: [Mandalorian Wars, commandedByOnRepublicSide, Revan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandedByOnRepublicSide Context triple: [Mandalorian Wars, commandedByOnRepublicSide, Revan]
-
A.
commandedBySide
Indicates that an action, unit, or operation is under the authority or control of a specified side or faction.
-
B.
commandedBy
chosen
Indicates that one entity holds authoritative control or issues orders over another entity.
-
C.
commanderForNationalists
Indicates that a person serves as a military commander leading or directing forces aligned with a nationalist faction or movement.
-
D.
capturedUnderCommandOf
Indicates that one entity was captured while operating under the authority, leadership, or command of another entity.
-
E.
commanderOfVictoriousSide
Indicates that one entity served as the commanding leader of the side that achieved victory in a conflict or competition relative to another entity.
- 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_69f2248108208190be60bf1af343ce70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 29, 2026, 7:36 p.m.