Triple
T29616661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zabrak |
E754880
|
entity |
| Predicate | notableDarkSideUser |
P207156
|
FINISHED |
| Object | Darth Maul |
E207462
|
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: Darth Maul | Statement: [Zabrak, notableDarkSideUser, Darth Maul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDarkSideUser Context triple: [Zabrak, notableDarkSideUser, Darth Maul]
-
A.
notableAdversary
Indicates that one entity is recognized as a significant or prominent opponent or rival of another entity.
-
B.
notableUser
Indicates that the user holds a special or distinguished status, such as being recognized, influential, or otherwise noteworthy within a given context.
-
C.
notableInformant
Indicates that one entity serves as a significant or well-known source of information or testimony for another entity.
-
D.
notableTurncoat
Indicates that an entity is recognized for having betrayed or switched allegiance from one side, group, or cause to another.
-
E.
notableFriend
Indicates that one entity is a friend of another in a way that is especially prominent, well-known, or significant.
- 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_6a277bf396f8819083e2c5ee9e9f677e |
completed | June 9, 2026, 2:35 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.