Triple
T16347939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smohain |
E396981
|
entity |
| Predicate | nearHistoricalEventDate |
P123065
|
FINISHED |
| Object | 18 June 1815 |
—
|
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: 18 June 1815 | Statement: [Smohain, nearHistoricalEventDate, 18 June 1815]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearHistoricalEventDate Context triple: [Smohain, nearHistoricalEventDate, 18 June 1815]
-
A.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
B.
notableEventDate
Indicates the date on which a notable or significant event associated with the subject occurred.
-
C.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
D.
timeOfEventCommemorated
Indicates the specific time or date at which the event being commemorated originally occurred.
-
E.
notableEventTime
Indicates the specific time at which a notable or significant event occurred.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da1038d88190b8292cfe71bc4f2a |
completed | April 18, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:07 a.m.