Triple
T16185709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J. Sterling Morton |
E392793
|
entity |
| Predicate | inceptionOfArborDay |
P28424
|
FINISHED |
| Object | 1872-04-10 |
—
|
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: 1872-04-10 | Statement: [J. Sterling Morton, inceptionOfArborDay, 1872-04-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inceptionOfArborDay Context triple: [J. Sterling Morton, inceptionOfArborDay, 1872-04-10]
-
A.
originalInaugurationDate
Indicates the date on which an entity (such as an office, institution, or facility) was first formally inaugurated or put into official operation.
-
B.
dateOfFirstProclamation
Indicates the specific date on which something (such as a law, declaration, or official statement) was first formally proclaimed or announced.
-
C.
isFoundedOn
Indicates that one entity is established, created, or based upon another entity as its foundational source or principle.
-
D.
foundedOn
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
-
E.
firstOfficialCommemorationDate
chosen
Indicates the calendar date on which something was formally and officially commemorated for the first time.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22060dcf88190b7c662946a5f0191 |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.