Triple
T11546450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ripto |
E273785
|
entity |
| Predicate | bossType |
P98692
|
FINISHED |
| Object | final boss in Spyro 2: Ripto's Rage! |
—
|
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: final boss in Spyro 2: Ripto's Rage! | Statement: [Ripto, bossType, final boss in Spyro 2: Ripto's Rage!]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bossType Context triple: [Ripto, bossType, final boss in Spyro 2: Ripto's Rage!]
-
A.
bossFeature
Indicates that one entity serves as a primary or dominant feature, element, or component in relation to another.
-
B.
bossCharacter
chosen
Indicates that one character serves as the primary, often more powerful, opponent or leader that others must confront or overcome.
-
C.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
-
D.
employerType
Indicates the classification or category of an employer in relation to the entity (e.g., public, private, nonprofit, self-employed).
-
E.
hasBoss
Indicates that one entity serves as the direct superior or manager of another entity in a hierarchical relationship.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e3ad548190b2c88332f5d919bd |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.