Triple
T38641289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Hemp |
E938599
|
entity |
| Predicate | hasApproximateDeathYear |
P26944
|
FINISHED |
| Object | 1901 |
—
|
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: 1901 | Statement: [Old Hemp, hasApproximateDeathYear, 1901]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateDeathYear Context triple: [Old Hemp, hasApproximateDeathYear, 1901]
-
A.
deathYearApproximate
chosen
Indicates that the year of an entity’s death is known only approximately rather than as an exact calendar year.
-
B.
approximateAgeAtDeath
Indicates the estimated age a person or entity was when they died, typically used when the exact age is unknown.
-
C.
estimatedDateOfDeath
Indicates the date on which an entity is believed or calculated to have died, rather than a precisely known death date.
-
D.
livedApproximately
Indicates that an entity’s lifespan or period of residence is known only roughly, with approximate rather than exact dates.
-
E.
deathYearInvestigated
Indicates that an entity’s year of death has been the subject of investigation or inquiry.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: May 3, 2026, 4:32 p.m.