Triple
T27994709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Arena League |
E706977
|
entity |
| Predicate | hasGameEnvironment |
P13810
|
FINISHED |
| Object | played in arenas |
—
|
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: played in arenas | Statement: [National Arena League, hasGameEnvironment, played in arenas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGameEnvironment Context triple: [National Arena League, hasGameEnvironment, played in arenas]
-
A.
hasGameSystem
Indicates that an item, product, or context is associated with or supports a particular game system or rules framework.
-
B.
hasEnvironmentType
chosen
Indicates that an entity is associated with or occurs within a specific type or category of environment.
-
C.
supportsGameEngine
Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or integration of a particular game engine.
-
D.
hasGameType
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
-
E.
hasTrainingEnvironment
Indicates that an entity is associated with, or operates within, a specific environment or setting used for training or practice.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 7:52 p.m.