Triple
T37592246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loatheb |
E935287
|
entity |
| Predicate | typeInGameData |
P182181
|
FINISHED |
| Object | Aberration |
—
|
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: Aberration | Statement: [Loatheb, typeInGameData, Aberration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeInGameData Context triple: [Loatheb, typeInGameData, Aberration]
-
A.
inGameType
chosen
Indicates that an entity participates in or belongs to a specific type or category within a game (e.g., game mode, classification, or role).
-
B.
game7Type
Indicates that the relationship specifies the type or category of a particular Game 7 in a series or competition.
-
C.
typicalGame
Indicates a relationship where one entity is characterized as a standard, representative, or commonly occurring example of a game for the other entity or context.
-
D.
notableGameType
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
-
E.
ballGameType
Indicates the specific kind or category of ball game associated with an event or activity.
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.