Triple
T21711790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Tmolus (mythological) |
E535922
|
entity |
| Predicate | consequenceOfContest |
P59870
|
FINISHED |
| Object | Midas given donkey ears |
—
|
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: Midas given donkey ears | Statement: [Mount Tmolus (mythological), consequenceOfContest, Midas given donkey ears]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceOfContest Context triple: [Mount Tmolus (mythological), consequenceOfContest, Midas given donkey ears]
-
A.
resultContested
Indicates that the outcome or result of an event, process, or decision is being challenged or disputed by one or more parties.
-
B.
consequenceOfInfluence
Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by another.
-
C.
losesContestTo
Indicates that one participant is defeated by another in a contest or competition.
-
D.
consequenceForOpponents
Indicates that one party’s actions or status result in negative outcomes, penalties, or repercussions specifically for their opponents.
-
E.
outcomeOf
chosen
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb53450108190ba1c9e3cc3a0ab89 |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:46 p.m.