Triple
T37467820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flame |
E931074
|
entity |
| Predicate | controlsSimilarTo |
P199514
|
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: [Flame, controlsSimilarTo, Spyro the Dragon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsSimilarTo Context triple: [Flame, controlsSimilarTo, Spyro the Dragon]
-
A.
controlsWith
Indicates that one entity exercises authority, direction, or regulatory power over another entity through specific means or mechanisms.
-
B.
lessSimilarTo
Indicates that one entity is considered to share fewer similarities or a weaker resemblance with another entity compared to some reference or alternative.
-
C.
userInterfaceSimilarTo
Indicates that one user interface resembles or closely matches another in appearance, layout, or interaction style.
-
D.
moreSimilarTo
Indicates that one entity bears a greater degree of similarity to a second entity than to a third entity, according to some defined similarity measure.
-
E.
controlsType
Indicates that one entity has authority over, or the ability to direct or regulate, the type or category of another entity.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
| PDg | Predicate description generation | batch_69ff3fb151008190bf8a90f9f1c5f0c8 |
completed | May 9, 2026, 2:07 p.m. |
Created at: May 3, 2026, 4:17 p.m.