Triple
T21029060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Κάδμος |
E518016
|
entity |
| Predicate | receivedOracleTo |
P20389
|
FINISHED |
| Object | follow a cow and found a city where it lay down |
—
|
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: follow a cow and found a city where it lay down | Statement: [Κάδμος, receivedOracleTo, follow a cow and found a city where it lay down]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedOracleTo Context triple: [Κάδμος, receivedOracleTo, follow a cow and found a city where it lay down]
-
A.
hasOracleOf
Indicates that one entity serves as a prophetic or divinatory source (an oracle) for another entity.
-
B.
commandedByOracleTo
chosen
Indicates that an entity performs or undertakes an action as a result of being ordered or instructed to do so by an oracle.
-
C.
deliveredOracleConcerning
Indicates that one entity proclaimed or communicated a divine message or prophetic oracle concerning another entity or topic.
-
D.
receivedSupportFrom
Indicates that one entity obtained help, resources, or backing from another entity.
-
E.
receivedPromiseAbout
Indicates that one entity has been given an assurance or commitment concerning another entity or event by some source.
- 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc7fd3ec81908ac237047f9b0d7a |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:55 p.m.