Triple
T32619014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire Giants |
E833868
|
entity |
| Predicate | typicalRoleInFantasy |
P145175
|
FINISHED |
| Object | powerful antagonists |
—
|
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: powerful antagonists | Statement: [Fire Giants, typicalRoleInFantasy, powerful antagonists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRoleInFantasy Context triple: [Fire Giants, typicalRoleInFantasy, powerful antagonists]
-
A.
fantasyRole
chosen
Indicates that one entity holds a fictional, imaginative, or role-playing identity or function in relation to another within a fantasy or make-believe context.
-
B.
roleInFables
Indicates that an entity serves a particular narrative or functional role within one or more fables.
-
C.
roleInSpearOfDestiny
Indicates that an entity has a specific role or involvement in the context of the Spear of Destiny.
-
D.
roleInRiseOfShadows
Indicates the specific part or function an entity plays within the context of the "Rise of Shadows" event or storyline.
-
E.
roleInFableIII
Indicates that an entity has a specific role or function within the context of the work "Fable III."
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:06 a.m.