Triple
T36145825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Susan |
E1045444
|
entity |
| Predicate | timeOfDeathRelativeToPlot |
P175378
|
FINISHED |
| Object | before main events of Romeo and Juliet |
—
|
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: before main events of Romeo and Juliet | Statement: [Susan, timeOfDeathRelativeToPlot, before main events of Romeo and Juliet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfDeathRelativeToPlot Context triple: [Susan, timeOfDeathRelativeToPlot, before main events of Romeo and Juliet]
-
A.
timeOfDeath
Indicates the specific time at which an entity (typically a person or organism) died.
-
B.
timeBeforeDeath
Indicates that the associated time value occurs prior to an entity’s death or moment of dying.
-
C.
deathTimeRelative
chosen
Indicates the time of a death expressed relative to another reference time or event, rather than as an absolute timestamp.
-
D.
timeInTomb
Indicates the duration that an entity remains or has remained inside a tomb.
-
E.
fictionalTimeToImpact
Indicates the amount of time, within a fictional or hypothetical context, remaining until a specified impact event occurs.
- 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_69f76e37ace88190a906b107d388f5d1 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 3, 2026, 4:08 p.m.