Triple
T27139264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red (Pokémon) |
E681770
|
entity |
| Predicate | commonStarterChoice |
P177176
|
FINISHED |
| Object | Bulbasaur |
—
|
NE NERFINISHED |
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: Bulbasaur | Statement: [Red (Pokémon), commonStarterChoice, Bulbasaur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonStarterChoice Context triple: [Red (Pokémon), commonStarterChoice, Bulbasaur]
-
A.
starterType
Indicates the classification or category of a starter (e.g., initial component, opening item, or first phase) associated with an entity or process.
-
B.
coordinateChoice
chosen
Indicates that one option is selected from a set of mutually exclusive alternatives within a coordinated choice structure.
-
C.
traditionalStart
Indicates that an event, process, or sequence begins in the customary or historically established way.
-
D.
typicalStartType
Indicates the usual or most common type or category in which something begins or is initiated.
-
E.
initialOpening
Indicates the first or earliest instance in which something is opened, begun, or made accessible.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 27, 2026, 9:08 a.m.