Triple
T37825365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daniel Horsmanden |
E943042
|
entity |
| Predicate | notableWorkDate |
P40005
|
FINISHED |
| Object | 1744 |
—
|
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: 1744 | Statement: [Daniel Horsmanden, notableWorkDate, 1744]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorkDate Context triple: [Daniel Horsmanden, notableWorkDate, 1744]
-
A.
notableWorkPublicationDate
Indicates the date on which a notable work associated with an entity was first published.
-
B.
notableWorkPeriodStart
Indicates the point in time when an entity’s period of producing its notable work or works begins.
-
C.
notableWorkYear
chosen
Indicates the year in which a notable work associated with an entity was created, released, or achieved prominence.
-
D.
notableEventDate
Indicates the date on which a notable or significant event associated with the subject occurred.
-
E.
notableWorkPeriod
Indicates the time span during which an entity produced or was associated with its most significant or well-known works.
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.