Triple
T17989689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The House of Pain |
E430333
|
entity |
| Predicate | supporterBehavior |
P130036
|
FINISHED |
| Object | vocal support for home team |
—
|
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: vocal support for home team | Statement: [The House of Pain, supporterBehavior, vocal support for home team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supporterBehavior Context triple: [The House of Pain, supporterBehavior, vocal support for home team]
-
A.
supporters
Indicates a relationship where one entity backs, endorses, or actively helps another entity, cause, or position.
-
B.
supporter
Indicates a relationship where one entity backs, advocates for, or provides assistance to another entity, often in an ongoing or affiliative way.
-
C.
opponentSupporters
Indicates that the related entities are supporters or backers of opposing sides in a contest, conflict, or competition.
-
D.
supporterPosition
Indicates the role, stance, or location that a supporter holds in relation to the entity or issue they support.
-
E.
supporterMovement
Indicates that an entity moves in support of, or as part of, the movement or progression of another entity.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b29e47a88190be58b79c73d3e652 |
completed | April 19, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:23 a.m.