Triple
T36963839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howlers gang |
E914375
|
entity |
| Predicate | enemyFactionOf |
P53524
|
FINISHED |
| Object | Vice Overseer Liam Byrne |
—
|
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: Vice Overseer Liam Byrne | Statement: [Howlers gang, enemyFactionOf, Vice Overseer Liam Byrne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enemyFactionOf Context triple: [Howlers gang, enemyFactionOf, Vice Overseer Liam Byrne]
-
A.
hasOpposingFaction
chosen
Indicates that one faction stands in opposition or conflict to another faction.
-
B.
enemyNation
Indicates that one nation is considered a hostile or adversarial state in relation to another nation.
-
C.
archenemyOf
Indicates a relationship in which one entity is the principal or most important enemy of another, often characterized by deep, ongoing opposition or rivalry.
-
D.
opponentForceAllegiance
Indicates that one force, group, or individual is aligned with or belongs to an opposing or enemy side in a conflict or competition.
-
E.
warAdversary
Indicates that two entities are opponents or enemies engaged in a state of war or armed conflict.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.