Triple
T4608208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cactus League spring training |
E100487
|
entity |
| Predicate | typicalGameType |
P10208
|
FINISHED |
| Object | exhibition game |
—
|
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: exhibition game | Statement: [Cactus League spring training, typicalGameType, exhibition game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGameType Context triple: [Cactus League spring training, typicalGameType, exhibition game]
-
A.
notableGameType
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
-
B.
hasGameType
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
-
C.
includesGameType
chosen
Indicates that one entity contains or supports a particular type or category of game.
-
D.
traditionalGame
Indicates that the relationship involves playing, practicing, or being associated with a game that is rooted in longstanding cultural or historical traditions.
-
E.
primaryGameMode
Indicates the main or default game mode associated with a particular game or gaming context.
- 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_69bd43cce1e08190a07d53af6a9b6c24 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd599debdc81909d11d0e871c666bb |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522e2d5c8190937d0b5574f78f99 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.