Triple
T30638351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romaine Heilger |
E779905
|
entity |
| Predicate | testimonyRole |
P164566
|
FINISHED |
| Object | crucial to the murder trial |
—
|
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: crucial to the murder trial | Statement: [Romaine Heilger, testimonyRole, crucial to the murder trial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testimonyRole Context triple: [Romaine Heilger, testimonyRole, crucial to the murder trial]
-
A.
gaveTestimonyIn
Indicates that one entity provided formal testimony or a statement in an official proceeding, event, or context associated with another entity.
-
B.
testimonyCharacteristic
chosen
Indicates that a particular quality, feature, or attribute is being ascribed to a testimony or statement given by an entity.
-
C.
juryRole
Indicates that an entity serves in the capacity or function of a juror within a judicial or decision-making process.
-
D.
viewOnTestimony
Indicates a stance or evaluation someone holds regarding the credibility, role, or use of testimony as a source of knowledge or evidence.
-
E.
testimonyTopic
Indicates that the content or subject matter of a given testimony is about a specified topic.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a537fb48190a92739f0addc6df1 |
completed | May 2, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:29 p.m.