Triple
T23783031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theseus and the Crommyonian Sow |
E587868
|
entity |
| Predicate | heroicArchetype |
P102015
|
FINISHED |
| Object | monster-slaying hero |
—
|
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: monster-slaying hero | Statement: [Theseus and the Crommyonian Sow, heroicArchetype, monster-slaying hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heroicArchetype Context triple: [Theseus and the Crommyonian Sow, heroicArchetype, monster-slaying hero]
-
A.
heroClass
Indicates the character class or role that a hero belongs to within a given system or context.
-
B.
usesCharacterArchetype
chosen
Indicates that one entity employs or incorporates the character archetype represented by another entity in its narrative or design.
-
C.
heroDepicted
Indicates that one entity is portrayed or represented as a hero in relation to another entity.
-
D.
protagonistType
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
E.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
- 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_69e2490f4ad48190b690878eec3596c6 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c62ea9c0819083544822267d3215 |
completed | April 29, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:16 p.m.