Triple
T7449106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Periphetes |
E171959
|
entity |
| Predicate | moralFunctionInMyth |
P46472
|
FINISHED |
| Object | exemplifies Theseus’ role as civilizing 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: exemplifies Theseus’ role as civilizing hero | Statement: [Periphetes, moralFunctionInMyth, exemplifies Theseus’ role as civilizing hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moralFunctionInMyth Context triple: [Periphetes, moralFunctionInMyth, exemplifies Theseus’ role as civilizing hero]
-
A.
moralOfMyth
Indicates the underlying lesson, ethical teaching, or message conveyed by a myth.
-
B.
moralTheme
Indicates that a work, event, or situation embodies or conveys a particular ethical lesson, value, or moral principle.
-
C.
moralConcept
Indicates that one entity represents or embodies a moral or ethical concept in relation to another.
-
D.
hasMoralFunction
chosen
Indicates that an entity serves or fulfills a role related to moral or ethical considerations.
-
E.
derivesMoralityFrom
Indicates that one entity bases or grounds its moral principles, judgments, or ethical framework on another entity.
- 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_69c68a65402881908f7869368eb746fb |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f389ddd48190a4b8753c67220c4f |
completed | March 27, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c6f039f7248190bb4183f97b605763 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:14 p.m.