Triple
T38610961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Mayo |
E934475
|
entity |
| Predicate | workWonPrize |
P73784
|
FINISHED |
| Object | Pulitzer Prize for Drama (for Beyond the Horizon) |
—
|
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: Pulitzer Prize for Drama (for Beyond the Horizon) | Statement: [Robert Mayo, workWonPrize, Pulitzer Prize for Drama (for Beyond the Horizon)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workWonPrize Context triple: [Robert Mayo, workWonPrize, Pulitzer Prize for Drama (for Beyond the Horizon)]
-
A.
tookPrize
Indicates that one entity received or accepted a prize or award from another entity or event.
-
B.
winnerWork
chosen
Indicates that a particular work (such as a book, film, or piece of art) is the one that won a specified award or competition.
-
C.
isPrizedFor
Indicates that something is highly valued or esteemed because of a particular quality, feature, or benefit it provides.
-
D.
competitionWonWith
Indicates that a competition was won using, involving, or in association with a particular participant, method, tool, or resource.
-
E.
eventWon
Indicates that an entity has achieved victory or first place in a specified event or competition.
- 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.