Triple
T28990396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonic the Hedgehog 3 |
E734809
|
entity |
| Predicate | introducesPlayableCharacter |
P43877
|
FINISHED |
| Object | Knuckles the Echidna |
—
|
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: Knuckles the Echidna | Statement: [Sonic the Hedgehog 3, introducesPlayableCharacter, Knuckles the Echidna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducesPlayableCharacter Context triple: [Sonic the Hedgehog 3, introducesPlayableCharacter, Knuckles the Echidna]
-
A.
playableCharacterFormOf
Indicates that one entity is a specific form or version of another entity as it appears as a playable character.
-
B.
hasPlayableCharacter
chosen
Indicates that an entity includes or is associated with a character that a user can control or play as.
-
C.
rideableCharacter
Indicates that one character can be mounted and ridden by another character as a means of transportation or control.
-
D.
mainCharacterField
Indicates that one entity is designated as the primary or central character associated with another entity, such as a work or narrative.
-
E.
mainCharacterCodeNumber
Indicates that an entity is identified as the primary or central character by a specific code number.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 28, 2026, 9:17 a.m.