Triple
T37538658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spyro: Year of the Dragon |
E933271
|
entity |
| Predicate | numberOfHomeworlds |
P205959
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Spyro: Year of the Dragon, numberOfHomeworlds, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfHomeworlds Context triple: [Spyro: Year of the Dragon, numberOfHomeworlds, 4]
-
A.
homeworldType
Indicates the type or classification of a subject’s homeworld (e.g., planet, moon, habitat) in relation to that subject.
-
B.
isMultipleStarSystem
Indicates that a star system contains two or more stars gravitationally bound together, rather than a single isolated star.
-
C.
hasInUniverseInhabitants
Indicates that a universe or fictional setting contains certain beings or populations as its inhabitants.
-
D.
homeworldStatus
Indicates the status or condition of an entity’s homeworld in relation to that entity (e.g., origin, current state, or affiliation of the homeworld).
-
E.
formerHomeworldOf
Indicates that a given place was once the primary planet or world of origin for a particular group, species, or civilization but no longer holds that status.
- F. None of above. chosen
Provenance (4 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:17 p.m.