Triple
T25404838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minyan Orchomenus |
E636523
|
entity |
| Predicate | hasNameInMythology |
P91943
|
FINISHED |
| Object | Orchomenus |
—
|
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: Orchomenus | Statement: [Minyan Orchomenus, hasNameInMythology, Orchomenus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInMythology Context triple: [Minyan Orchomenus, hasNameInMythology, Orchomenus]
-
A.
hasMythologicalNamesake
chosen
Indicates that one entity is named after, or shares its name with, a figure or element from mythology.
-
B.
hasNameInReligionOrFolklore
Indicates that an entity is known by a particular name specifically within a religious or folkloric tradition.
-
C.
isMythologicalFigureType
Indicates that one entity is classified as a specific type or category of mythological figure in relation to another entity.
-
D.
linkedToMythology
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
E.
mythologicalTextMention
Indicates that a mythological text mentions, references, or otherwise explicitly refers to a given entity or concept.
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 1:52 p.m.