Triple
T37438495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andy LaPlegua |
E930342
|
entity |
| Predicate | usedToPlayIn |
P120854
|
FINISHED |
| Object | hardcore band Lash Out |
—
|
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: hardcore band Lash Out | Statement: [Andy LaPlegua, usedToPlayIn, hardcore band Lash Out]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToPlayIn Context triple: [Andy LaPlegua, usedToPlayIn, hardcore band Lash Out]
-
A.
isUsedToPlay
Indicates that something serves as an instrument, tool, or medium for engaging in a game, sport, or other form of play.
-
B.
oftenPlayedDuring
Indicates that one thing (such as a song, piece, or media) is frequently played in the context, time, or situation associated with another.
-
C.
formerlyPlayedIn
chosen
Indicates that an entity was previously a member of or participated in a particular team, group, or organization in the past but no longer does so.
-
D.
playedWith
Indicates that one entity engaged in play or a playful activity together with another entity.
-
E.
usedInSport
Indicates that something (such as an object, technique, or concept) is employed or utilized within the context of a particular sport.
- 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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.