Triple
T11997308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friar Laurence |
E285563
|
entity |
| Predicate | planOutcome |
P102601
|
FINISHED |
| Object | tragic failure |
—
|
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: tragic failure | Statement: [Friar Laurence, planOutcome, tragic failure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planOutcome Context triple: [Friar Laurence, planOutcome, tragic failure]
-
A.
proposalOutcome
Indicates the result or status assigned to a proposal after it has been evaluated or decided upon.
-
B.
projectOutcome
Indicates the resulting state, impact, or consequences produced by carrying out a project.
-
C.
plan
Indicates that an entity intends or arranges for a future action or sequence of actions to occur.
-
D.
missionOutcome
Indicates the result or consequence of a mission, specifying whether and how the mission’s objectives were achieved or failed.
-
E.
programOutcome
Indicates the resulting state, effect, or consequence produced by executing or completing a program.
- F. None of above. chosen
Provenance (4 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903c172788190b92042e9d10a48bf |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d9038e39f881908c58c19802ba2eb0 |
completed | April 10, 2026, 2:05 p.m. |
Created at: April 8, 2026, 9:46 p.m.