Triple
T29991146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackhammer |
E761881
|
entity |
| Predicate | finisherFor |
P168329
|
FINISHED |
| Object | Bill Goldberg |
—
|
NE NERFINISHED |
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: Bill Goldberg | Statement: [Jackhammer, finisherFor, Bill Goldberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finisherFor Context triple: [Jackhammer, finisherFor, Bill Goldberg]
-
A.
finisher
Indicates that an entity completes, concludes, or brings to an end a process, event, or sequence, often as the final actor or decisive contributor.
-
B.
finishingMethod
Indicates the technique or process used to complete or finalize an object, task, or work.
-
C.
finishType
Indicates the manner or outcome by which an action, process, or event is completed.
-
D.
hasFinisherNameMeaning
Indicates that an entity’s finishing move is associated with a specific meaning or interpretation of its name.
-
E.
finish
Indicates that an entity brings an action, process, or state to an end or completion.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6791aa82c8190afb7c808cddbf46a |
completed | May 2, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:38 p.m.