Triple
T34900483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spyro: Attack of the Rhynocs |
E1006570
|
entity |
| Predicate | featuresCollectible |
P54721
|
FINISHED |
| Object | gems |
—
|
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: gems | Statement: [Spyro: Attack of the Rhynocs, featuresCollectible, gems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCollectible Context triple: [Spyro: Attack of the Rhynocs, featuresCollectible, gems]
-
A.
featuresItem
chosen
Indicates that one entity includes, presents, or highlights another entity as a notable item or component.
-
B.
collectibleFor
Indicates that one entity is intended or suitable to be collected by, or kept as part of a collection for, another entity.
-
C.
collectibleAspect
Indicates that one entity represents a collectible-related characteristic, feature, or dimension associated with another entity.
-
D.
collectionFeature
Indicates that a collection possesses or is characterized by a particular feature or attribute.
-
E.
usesCollectible
Indicates that one entity employs or makes use of a collectible item in performing an action or fulfilling a function.
- 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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0379a4086c8190a83df5570f737e15 |
completed | May 12, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_6a037049db848190a6268bf1a8a60223 |
completed | May 12, 2026, 6:24 p.m. |
Created at: May 3, 2026, 4 p.m.