Triple
T6914193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Of Revenge |
E160007
|
entity |
| Predicate | positionOnRevenge |
P74116
|
FINISHED |
| Object | discourages private revenge |
—
|
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: discourages private revenge | Statement: [Of Revenge, positionOnRevenge, discourages private revenge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnRevenge Context triple: [Of Revenge, positionOnRevenge, discourages private revenge]
-
A.
positionOnReason
Indicates that one entity holds a particular stance, justification, or rationale concerning another entity or issue.
-
B.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
positionOnCrime
Indicates a stance, opinion, or policy position that an entity holds regarding crime or crime-related issues.
-
D.
positionOnIdentity
Indicates a stance, view, or opinion that an entity holds regarding identity-related issues or characteristics.
-
E.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
- 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_69c6883ab1008190a07129ff06f625d9 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9dda4108190a79a7841b0658a4d |
completed | March 27, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:26 p.m.