Triple
T20012508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bassanio |
E494622
|
entity |
| Predicate | rejectsCasket |
P438
|
FINISHED |
| Object | gold casket |
—
|
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: gold casket | Statement: [Bassanio, rejectsCasket, gold casket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rejectsCasket Context triple: [Bassanio, rejectsCasket, gold casket]
-
A.
rejectedIn
Indicates that an entity or proposal was not accepted or was turned down within a specific context, process, or location.
-
B.
rejectedBy
chosen
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
C.
rejectedBecause
Indicates that one entity refused, dismissed, or did not accept another entity specifically due to a stated reason or cause.
-
D.
resultOfRejection
Indicates that something occurs as a consequence or outcome of a prior act of rejection.
-
E.
rejectedAt
Indicates the time or date at which something (such as a request, application, or proposal) was formally rejected.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66238f434819083b11458179bb601 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:34 p.m.