Triple
T36963840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howlers gang |
E914375
|
entity |
| Predicate | alignmentInGame |
P186813
|
FINISHED |
| Object | hostile NPC faction |
—
|
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: hostile NPC faction | Statement: [Howlers gang, alignmentInGame, hostile NPC faction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alignmentInGame Context triple: [Howlers gang, alignmentInGame, hostile NPC faction]
-
A.
alignmentWithProtagonist
Indicates the degree to which an entity’s goals, actions, or loyalties are supportive of, neutral toward, or opposed to the protagonist.
-
B.
alignmentGoal
Indicates that an entity has a desired or target alignment state it aims to achieve or maintain.
-
C.
alignmentInSeries
Indicates that one entity’s position or orientation is arranged in a specific way relative to others within an ordered sequence or series.
-
D.
alignmentWithToons
Indicates that one entity’s stance, behavior, or attributes are in agreement or harmony with those of "Toons."
-
E.
alignmentShape
Indicates that one entity’s shape is arranged, oriented, or matched in position relative to another entity’s shape.
- F. None of above. chosen
Provenance (4 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_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fa0a799b9081909bfa8293a22c4b00 |
completed | May 5, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:14 p.m.