Triple
T5079912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metroid |
E114487
|
entity |
| Predicate | typicalGameplayElement |
P39812
|
FINISHED |
| Object | exploration of interconnected areas |
—
|
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: exploration of interconnected areas | Statement: [Metroid, typicalGameplayElement, exploration of interconnected areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGameplayElement Context triple: [Metroid, typicalGameplayElement, exploration of interconnected areas]
-
A.
gameElement
Indicates that one entity functions as a component, feature, or part within the structure or mechanics of a game.
-
B.
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.
-
C.
performedInGame
Indicates that an action or event was carried out during a particular game or match.
-
D.
playInGameIntroduced
Indicates that an entity participates as a playable element within the specific game in which it was first introduced.
-
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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74f86c988190aa026073ed435a45 |
completed | March 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69bd7159adc881909effd4382c395c66 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.