Triple
T18152752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Asakai |
E434547
|
entity |
| Predicate | hasGameMechanicContext |
P39812
|
FINISHED |
| Object | capital ship jump mechanics |
—
|
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: capital ship jump mechanics | Statement: [Battle of Asakai, hasGameMechanicContext, capital ship jump mechanics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGameMechanicContext Context triple: [Battle of Asakai, hasGameMechanicContext, capital ship jump mechanics]
-
A.
gameplayMechanic
chosen
Indicates a relationship where one entity functions as a rule, system, or interactive feature that defines how another entity can be played or operated within a game.
-
B.
notableLevelMechanic
Indicates that an entity is recognized for its significant involvement in designing, implementing, or innovating game level mechanics.
-
C.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
D.
hasGameSystem
Indicates that an item, product, or context is associated with or supports a particular game system or rules framework.
-
E.
gameContext
Indicates the situational framework or environment in which a game’s actions, rules, and interactions take place.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de39a8f481908d1752767d0aae0e |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.