Triple
T22053942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glaucus |
E544955
|
entity |
| Predicate | connectedLegend |
P1582
|
FINISHED |
| Object | Minos’ demand that Polyidus teach Glaucus divination |
—
|
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: Minos’ demand that Polyidus teach Glaucus divination | Statement: [Glaucus, connectedLegend, Minos’ demand that Polyidus teach Glaucus divination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedLegend Context triple: [Glaucus, connectedLegend, Minos’ demand that Polyidus teach Glaucus divination]
-
A.
hasLegendAssociatedWith
chosen
Indicates that something is connected to or accompanied by a traditional story, myth, or legend.
-
B.
mentionsLegend
Indicates that one entity makes reference to or cites a legendary figure, story, or concept associated with another entity.
-
C.
legendStatus
Indicates that an entity holds, is assigned, or is associated with a particular legend-related status or classification.
-
D.
inLegendRole
Indicates that an entity appears in a legendary or mythic context fulfilling a specific narrative or symbolic role.
-
E.
connectedLine
Indicates that two entities are joined by a continuous line or linear connection.
- 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12855c7708190a8de44837140b654 |
completed | April 28, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:26 p.m.