Triple
T38349922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jimmy Emmett |
E1041649
|
entity |
| Predicate | helpsCommit |
P190453
|
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: [Jimmy Emmett, helpsCommit, murder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpsCommit Context triple: [Jimmy Emmett, helpsCommit, murder]
-
A.
commitsTo
Indicates that one entity makes a promise or formal obligation to carry out a specific action or uphold a particular course of behavior toward another entity or goal.
-
B.
coreCommitment
Indicates a fundamental, central obligation or promise that defines the primary responsibility or dedication within a relationship or agreement.
-
C.
commitment
Indicates a sustained obligation or promise that binds an entity to a course of action, relationship, or goal over time.
-
D.
guaranteeCommitments
Indicates a relationship where one party formally assures that specific obligations or promises made to another party will be fulfilled or upheld.
-
E.
supportsCommittee
Indicates that one entity provides backing, endorsement, or assistance to a committee.
- 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_69f76e2ad95481908c920c0e5c1c3e26 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcc7a4d7f881908b43b960911b81e9 |
completed | May 7, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69fcc589720c819089c8f500fea3c86a |
completed | May 7, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fcc7a42f68819081d6ec8bb6b53438 |
completed | May 7, 2026, 5:11 p.m. |
Created at: May 3, 2026, 4:30 p.m.