Triple
T35699147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poosh 'Em Up |
E1031528
|
entity |
| Predicate | associatedLineup |
P96347
|
FINISHED |
| Object | Murderers' Row |
E1003230
|
NE 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: Murderers' Row | Statement: [Poosh 'Em Up, associatedLineup, Murderers' Row]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedLineup Context triple: [Poosh 'Em Up, associatedLineup, Murderers' Row]
-
A.
basedOnLineupsOf
Indicates that something is derived from, determined by, or constructed using specific lineups.
-
B.
associatedLeagueTeam
Indicates that one entity is a sports team that is formally linked or affiliated with a particular league.
-
C.
teamLineup
Indicates the assignment and ordering of participants or members that make up a specific team configuration for an event or activity.
-
D.
partOfLineup
chosen
Indicates that an entity is included as a member or component within a particular lineup or roster.
-
E.
associatedTeam
Indicates that one entity is linked or connected to a particular team, typically as its member, owner, or primary affiliation.
- F. None of above.
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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a387d0a20c881909f71135b97bf8fa7 |
completed | June 22, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.