Triple
T29616664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zabrak |
E754880
|
entity |
| Predicate | notableJedi |
P207157
|
FINISHED |
| Object | Eeth Koth |
E1733797
|
NE 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: Eeth Koth | Statement: [Zabrak, notableJedi, Eeth Koth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableJedi Context triple: [Zabrak, notableJedi, Eeth Koth]
-
A.
JediRank
Indicates the formal rank or level of status a Jedi holds within the Jedi Order hierarchy.
-
B.
notableStarfighter
Indicates that an entity is a starfighter recognized for particular significance, prominence, or distinction (e.g., historically, tactically, or culturally).
-
C.
notableSamurai
Indicates that the subject is recognized as a samurai of particular historical, cultural, or martial significance.
-
D.
distinctionFromSith
Indicates that one entity is explicitly characterized as being different or separate from Sith.
-
E.
SithRank
Indicates the hierarchical rank or level a Sith holds within the Sith order or structure.
- F. None of above. chosen
Provenance (5 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26616a5edc8190b621fa02880cbf68 |
completed | June 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 28, 2026, 6:32 p.m.