Triple
T37997351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belva Gaertner murder case |
E947995
|
entity |
| Predicate | involvedObject |
P1256
|
FINISHED |
| Object | automobile |
—
|
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: automobile | Statement: [Belva Gaertner murder case, involvedObject, automobile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedObject Context triple: [Belva Gaertner murder case, involvedObject, automobile]
-
A.
involvedAction
Indicates that an entity participates in, performs, or is otherwise engaged in a specified action or activity.
-
B.
stableInvolved
Indicates that an entity is consistently and reliably involved in a particular relationship, process, or activity over time.
-
C.
involvedBranch
Indicates that a particular branch (such as a location, division, or sub-unit) participates in, is associated with, or plays a role in the referenced event, process, or relationship.
-
D.
involves
chosen
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
E.
passInvolved
Indicates that an entity is involved in a passing action, either as the passer, receiver, or otherwise participating party.
- 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
Created at: May 3, 2026, 4:20 p.m.