Triple
T30228976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandalorian Wars |
E768570
|
entity |
| Predicate | mandalorianLeader |
P169001
|
FINISHED |
| Object | Mandalore the Ultimate |
—
|
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: Mandalore the Ultimate | Statement: [Mandalorian Wars, mandalorianLeader, Mandalore the Ultimate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mandalorianLeader Context triple: [Mandalorian Wars, mandalorianLeader, Mandalore the Ultimate]
-
A.
rebelsLeader
Indicates that one entity serves as the leader of a group of rebels associated with the other entity.
-
B.
roleInRogueOne
Indicates that an entity has a specific acting or production role in the film "Rogue One: A Star Wars Story."
-
C.
Vaapad
Indicates a specialized, aggressive lightsaber combat form or technique being used or referenced in relation to an entity.
-
D.
chiefLieutenantOf
Indicates that one person serves as the primary subordinate or top-ranking assistant to another leader or authority figure.
-
E.
roleDuringGalacticCivilWar
Indicates the specific function, position, or involvement an entity had during the Galactic Civil War.
- 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_69f2248108208190be60bf1af343ce70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6802486ac8190a936df82f2988383 |
completed | May 2, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 29, 2026, 7:36 p.m.