Triple
T19901925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sixth Labour of Heracles |
E478311
|
entity |
| Predicate | hasHeroicTheme |
P137758
|
FINISHED |
| Object | overcoming monstrous nature |
—
|
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: overcoming monstrous nature | Statement: [sixth Labour of Heracles, hasHeroicTheme, overcoming monstrous nature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeroicTheme Context triple: [sixth Labour of Heracles, hasHeroicTheme, overcoming monstrous nature]
-
A.
hasThemeSong
Indicates that an entity is associated with or characterized by a particular theme song.
-
B.
hasMainThemeCharacter
Indicates that a work (such as a story, film, or game) features a specific character as its central or primary thematic focus.
-
C.
hasNotableHero
Indicates that an entity is associated with a particularly distinguished or prominent hero.
-
D.
hasPrologueTheme
Indicates that a work’s prologue centers on, introduces, or is characterized by a particular thematic content or motif.
-
E.
hasMythicTheme
Indicates that something embodies, references, or is characterized by a mythic or mythological theme.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65943aefc81909e873e1845d5af3d |
completed | April 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:52 p.m.