Triple
T16383289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurytus |
E397859
|
entity |
| Predicate | offeredPrizeFor |
P81187
|
FINISHED |
| Object | victory in archery contest |
—
|
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: victory in archery contest | Statement: [Eurytus, offeredPrizeFor, victory in archery contest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredPrizeFor Context triple: [Eurytus, offeredPrizeFor, victory in archery contest]
-
A.
offeredRewardTo
Indicates that one entity has proposed or promised a reward to another entity, typically as an incentive for a specific action or outcome.
-
B.
offersAward
Indicates that one entity grants or makes available an award or prize to another entity.
-
C.
offersRewardFor
chosen
Indicates that one entity promises or provides a reward in exchange for another entity performing a specified action or achieving a particular outcome.
-
D.
offering
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
-
E.
isPrizedFor
Indicates that something is highly valued or esteemed because of a particular quality, feature, or benefit it provides.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319ddcef08190a2081855b5cf6762 |
completed | April 18, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.