Triple
T9534944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinbad and the Eye of the Tiger |
E229987
|
entity |
| Predicate | featuresCreatureEffects |
P83317
|
FINISHED |
| Object | saber-toothed tiger |
—
|
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: saber-toothed tiger | Statement: [Sinbad and the Eye of the Tiger, featuresCreatureEffects, saber-toothed tiger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCreatureEffects Context triple: [Sinbad and the Eye of the Tiger, featuresCreatureEffects, saber-toothed tiger]
-
A.
featuresMonster
Indicates that something includes or prominently presents a monster as part of its content or composition.
-
B.
specialEffectsBy
Indicates that the special effects for something (such as a film, scene, or shot) are created or provided by a particular person or entity.
-
C.
featuresCreatureOrLegend
chosen
Indicates that something includes, depicts, or prominently involves a particular creature or legendary being.
-
D.
usesCreature
Indicates that one entity employs, controls, or relies on a creature to perform an action or fulfill a function.
-
E.
eventEffect
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
- 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_69ca847b1b3081908f72bc932c17cc41 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98cc58bc8190ba921410e4b64aaa |
completed | April 1, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69cca56c44f88190a54a5d2a133bb07e |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 8 p.m.