Triple
T33646517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uglich tragedy |
E861974
|
entity |
| Predicate | hasDisputedVerdict |
P23974
|
FINISHED |
| Object | murder disguised as accident |
—
|
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: murder disguised as accident | Statement: [Uglich tragedy, hasDisputedVerdict, murder disguised as accident]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisputedVerdict Context triple: [Uglich tragedy, hasDisputedVerdict, murder disguised as accident]
-
A.
hasDisputedStatus
chosen
Indicates that the status or classification of something is contested, uncertain, or not universally agreed upon.
-
B.
hasDisputedStatusWith
Indicates that there is a contested or unresolved status, claim, or standing between the related entities.
-
C.
hasDisputedClause
Indicates that a particular clause within an agreement or document is subject to disagreement, challenge, or contention between involved parties.
-
D.
laterDisputedBy
Indicates that a previously made claim, statement, or assertion is subsequently challenged, questioned, or contradicted by another party.
-
E.
hasDisputeWith
Indicates that there is a conflict, disagreement, or contested issue between two entities.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
Created at: May 1, 2026, 1:42 a.m.