Triple
T31893760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Greek Myths |
E814219
|
entity |
| Predicate | includesMythCycle |
P137609
|
FINISHED |
| Object | Trojan War cycle |
—
|
NE NERFINISHED |
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: Trojan War cycle | Statement: [The Greek Myths, includesMythCycle, Trojan War cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesMythCycle Context triple: [The Greek Myths, includesMythCycle, Trojan War cycle]
-
A.
centralMythology
Indicates that one entity serves as a core or defining mythological element within the context or tradition of another entity.
-
B.
subsequentMythology
Indicates that one mythology develops later than, or is derived from, another mythology in time or tradition.
-
C.
mythologicalContent
chosen
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
-
D.
linkedToMythology
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
E.
eraOfMyth
Indicates a temporal relationship where an event, story, or phenomenon belongs to or takes place during a mythological or legendary era.
- 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a0191d96dc88190ac0823e534f9d704 |
completed | May 11, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_6a01908110448190a46442ffe4d15f5f |
completed | May 11, 2026, 8:17 a.m. |
Created at: April 30, 2026, 11:58 p.m.