Triple
T12087726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tybalt |
E287850
|
entity |
| Predicate | seeksRevengeFor |
P61789
|
FINISHED |
| Object | Romeo’s intrusion at the Capulet feast |
—
|
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: Romeo’s intrusion at the Capulet feast | Statement: [Tybalt, seeksRevengeFor, Romeo’s intrusion at the Capulet feast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seeksRevengeFor Context triple: [Tybalt, seeksRevengeFor, Romeo’s intrusion at the Capulet feast]
-
A.
causeOfVengeance
chosen
Indicates a relationship where one entity is the reason or trigger for another entity’s desire or act of vengeance.
-
B.
methodOfRevenge
Indicates a relationship where a specific action or strategy is used as the means by which revenge is carried out.
-
C.
isEmbittered
Indicates that an entity harbors persistent bitterness or resentment, typically as a result of past experiences or perceived wrongs.
-
D.
antagonistOf
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
-
E.
positionOnRevenge
Indicates a stance or attitude that one entity holds regarding the idea, acceptability, or pursuit of revenge.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9178ad99c8190a54777b9bbe998bc |
completed | April 10, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69d915000454819089fee00022055599 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.