Triple
T36549129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turbine, Inc. |
E901209
|
entity |
| Predicate | operatedGame |
P203613
|
FINISHED |
| Object | Asheron's Call |
E1786844
|
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: Asheron's Call | Statement: [Turbine, Inc., operatedGame, Asheron's Call]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedGame Context triple: [Turbine, Inc., operatedGame, Asheron's Call]
-
A.
toyGameInteraction
Indicates an interaction where an entity engages with a toy or game, such as playing with, manipulating, or otherwise using it.
-
B.
gameAct
Indicates that an entity performs or participates in an action or event within a game context.
-
C.
homeGamesState
Indicates the state or location context in which a team's home games are played.
-
D.
homeGameActivity
Indicates that an activity or event takes place as a home game for a particular team or participant.
-
E.
hasGameSystem
Indicates that an item, product, or context is associated with or supports a particular game system or rules framework.
- F. None of above. chosen
Provenance (5 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a01b31b233c819091974a06f7a76d4a |
completed | May 11, 2026, 10:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a380d26288190b2942b781d143306 |
completed | June 23, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_6a01b2c147008190bbf9e0fa1bbae1f3 |
completed | May 11, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_6a01b31a5b408190abde68df45a82c81 |
completed | May 11, 2026, 10:44 a.m. |
Created at: May 3, 2026, 4:11 p.m.