Triple
T25198455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spyro 2: Ripto's Rage! |
E631063
|
entity |
| Predicate | controlCharacter |
P98666
|
FINISHED |
| Object | Spyro the Dragon |
—
|
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: Spyro the Dragon | Statement: [Spyro 2: Ripto's Rage!, controlCharacter, Spyro the Dragon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlCharacter Context triple: [Spyro 2: Ripto's Rage!, controlCharacter, Spyro the Dragon]
-
A.
controllingCharacter
Indicates that one character exerts control, influence, or authority over another character.
-
B.
textCharacter
Indicates that one entity is a character (such as a letter, digit, or symbol) within a piece of text associated with another entity.
-
C.
hasCharacterControl
chosen
Indicates that one entity has the ability or authority to direct, manipulate, or govern the behavior or state of another entity.
-
D.
characterForm
Indicates that one entity is a particular form, version, or transformation state of a character.
-
E.
capturesCharacter
Indicates that one entity seizes, traps, or takes control of another character.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 21, 2026, 12:50 p.m.