Triple
T28899416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poison |
E732911
|
entity |
| Predicate | roleInFinalFight |
P83335
|
FINISHED |
| Object | enemy character |
—
|
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: enemy character | Statement: [Poison, roleInFinalFight, enemy character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInFinalFight Context triple: [Poison, roleInFinalFight, enemy character]
-
A.
roleInEndgame
chosen
Indicates that an entity has a specific function, position, or responsibility within the final or concluding phase of an event, process, or scenario.
-
B.
roleInMortalKombat
Indicates that one entity has a specific role or function within the context of the Mortal Kombat franchise or universe.
-
C.
endedCombatRole
Indicates that an entity has ceased or completed its previously active combat role or participation in hostilities.
-
D.
roleInCombatSystem
Indicates the specific function or responsibility an entity has within a combat or battle mechanics framework.
-
E.
roleInGigantomachy
Indicates the specific part or function an entity played in the mythological conflict known as the Gigantomachy.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: April 28, 2026, 8:01 a.m.