Triple
T35297082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | murder of Johnny Boz |
E1019401
|
entity |
| Predicate | suspectOccupation |
P66757
|
FINISHED |
| Object | crime novelist |
—
|
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: crime novelist | Statement: [murder of Johnny Boz, suspectOccupation, crime novelist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suspectOccupation Context triple: [murder of Johnny Boz, suspectOccupation, crime novelist]
-
A.
subjectOccupation
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
-
B.
allegedOccupation
chosen
Indicates that one entity is claimed or reported to be the occupation or job role of another entity, without asserting that this claim is necessarily true.
-
C.
recognizedOccupationOf
Indicates that one entity is acknowledged or officially accepted as the occupation or professional role held by another entity.
-
D.
occupationType
Indicates the specific kind or category of work, profession, or role that an entity performs or holds.
-
E.
involvedOccupationOf
Indicates that an entity participates in or is associated with a particular occupation or professional role.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7901dce2c8190869190a338ec336c |
completed | May 3, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.