Triple
T37539674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sith Inquisitor |
E933292
|
entity |
| Predicate | combatRoleOption |
P89121
|
FINISHED |
| Object | damage dealer |
—
|
LITERAL 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: damage dealer | Statement: [Sith Inquisitor, combatRoleOption, damage dealer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatRoleOption Context triple: [Sith Inquisitor, combatRoleOption, damage dealer]
-
A.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
roleInCombatSystem
chosen
Indicates the specific function or responsibility an entity has within a combat or battle mechanics framework.
-
C.
allowedCombatRoles
Indicates the combat roles that an entity is permitted or authorized to perform.
-
D.
favoredMilitaryRole
Indicates the military position, function, or specialization that an entity prefers or is most inclined to choose.
-
E.
endedCombatRole
Indicates that an entity has ceased or completed its previously active combat role or participation in hostilities.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.