Triple
T20193045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pokémon Ruby and Sapphire |
E493018
|
entity |
| Predicate | introducedDoubleBattles |
P139096
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Pokémon Ruby and Sapphire, introducedDoubleBattles, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedDoubleBattles Context triple: [Pokémon Ruby and Sapphire, introducedDoubleBattles, true]
-
A.
supportsDualPlayfield
Indicates that an entity is capable of handling or displaying two playfields or gameplay areas simultaneously.
-
B.
battedDoubles
Indicates that the subject hit a double in baseball, successfully reaching second base on a batted ball.
-
C.
usedInBattle
Indicates that something (typically a tool, strategy, or resource) was employed or applied during a battle or combat situation.
-
D.
coveredBattle
Indicates that an entity reported on, documented, or otherwise provided coverage of a particular battle or military engagement.
-
E.
introducedAsTrainer
Indicates that one entity is presented or identified to another entity in the role of a trainer.
- F. None of above. chosen
Provenance (4 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad7270081908ed8513a8363e9b1 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:37 p.m.