Triple
T11605075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenneth W. Hess |
E275234
|
entity |
| Predicate | investigationYear |
P100560
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Kenneth W. Hess, investigationYear, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: investigationYear Context triple: [Kenneth W. Hess, investigationYear, 2003]
-
A.
yearOfExecution
Indicates the specific calendar year in which an execution (such as a legal, contractual, or procedural act) took place.
-
B.
deploymentYear
Indicates the calendar year in which an entity (such as a system, product, or resource) was first put into active use or operation.
-
C.
depositionYear
Indicates the calendar year in which something (such as a document, sample, or item) was formally deposited or submitted.
-
D.
yearOfReference
Indicates the specific year to which a statement, measurement, or data point is intended to apply or be interpreted with reference.
-
E.
derivationYear
Indicates the year in which something was derived, produced, or generated from a source.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d895502e0081909ee9c3d45d26cd91 |
completed | April 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69d85dd20d188190863d1190d4c16048 |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:38 p.m.