Triple
T21162281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scrapper |
E521470
|
entity |
| Predicate | combinerTeamPosition |
P143114
|
FINISHED |
| Object | right leg of Devastator |
—
|
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: right leg of Devastator | Statement: [Scrapper, combinerTeamPosition, right leg of Devastator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combinerTeamPosition Context triple: [Scrapper, combinerTeamPosition, right leg of Devastator]
-
A.
notablePositionCombination
Indicates that an entity holds or has held a particularly significant combination of positions, roles, or offices considered notable when taken together.
-
B.
clubPosition
Indicates the specific role or position an individual holds within a sports club or team.
-
C.
partOfLineup
Indicates that an entity is included as a member or component within a particular lineup or roster.
-
D.
positionPlayedForTeam
Indicates the specific playing position or role an individual held while participating on a particular team.
-
E.
coachPositionPlayed
Indicates the role or position a coach played (typically as a player) in the sport they are associated with.
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72532e9348190ad37fe858843d0f5 |
completed | April 21, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 2:59 p.m.