Triple
T20221614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act III |
E495267
|
entity |
| Predicate | concludesWorkThat |
P27991
|
FINISHED |
| Object | won the Pulitzer Prize for Drama |
—
|
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: won the Pulitzer Prize for Drama | Statement: [Act III, concludesWorkThat, won the Pulitzer Prize for Drama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concludesWorkThat Context triple: [Act III, concludesWorkThat, won the Pulitzer Prize for Drama]
-
A.
concludesWork
Indicates that an entity finishes, completes, or brings to an end a particular piece of work or task.
-
B.
concludes
Indicates that one entity brings something (such as an event, process, or discussion) to an end or reaches a final decision or judgment about it.
-
C.
concludesIn
Indicates that an event, process, or action ends or reaches its final state within a specified time, place, or context.
-
D.
concludedWith
chosen
Indicates that an event, process, or interaction ended or was finalized by a specific outcome, action, or state.
-
E.
workOnItEnded
Indicates that an entity’s involvement in working on a particular task, project, or item has come to an end.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd610f881908fdd22b1f8bd2efc |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.