Triple
T34809834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meursault |
E1003466
|
entity |
| Predicate | isTriedFor |
P14998
|
FINISHED |
| Object | Murder |
—
|
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 | Statement: [Meursault, isTriedFor, Murder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTriedFor Context triple: [Meursault, isTriedFor, Murder]
-
A.
wasTriedAt
Indicates that a legal case or judicial proceeding involving an entity took place at a specific court or location.
-
B.
wasTriedFor
chosen
Indicates that a person or entity underwent a formal legal proceeding in which they were judged in relation to a specific alleged offense or charge.
-
C.
wasTriedAfter
Indicates that one trial or legal proceeding occurred subsequent to another in time.
-
D.
triedBy
Indicates that an entity has made an attempt to perform an action on, or in relation to, another entity.
-
E.
wasTriedBy
Indicates that a legal case or charge involving an entity was examined and judged in a trial conducted by another entity (such as a court or judge).
- 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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ab248748190858420c09bbdba32 |
completed | May 3, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.