Triple
T13388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abraham Lincoln |
E268
|
entity |
| Predicate | emancipationProclamationDate |
P1385
|
FINISHED |
| Object | 1863-01-01 |
—
|
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: 1863-01-01 | Statement: [Abraham Lincoln, emancipationProclamationDate, 1863-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emancipationProclamationDate Context triple: [Abraham Lincoln, emancipationProclamationDate, 1863-01-01]
-
A.
inaugurationDay
Indicates the specific day on which a formal ceremony is held to induct someone into an official position or office.
-
B.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
C.
foundedOn
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
-
D.
foundingDocument
Indicates that one entity serves as the official charter, constitution, or primary legal/organizational document that establishes or defines the other entity.
-
E.
announcementDate
Indicates the date on which an announcement is formally made or becomes publicly known.
- 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_69a23d7ad88c8190bffe8ab091d86642 |
completed | Feb. 28, 2026, 12:57 a.m. |
| NER | Named-entity recognition | batch_69a243abb2ec8190937365e5ecec52ad |
completed | Feb. 28, 2026, 1:23 a.m. |
| PD | Predicate disambiguation | batch_69a23fe9470c8190918a6ca1df168646 |
completed | Feb. 28, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69a243aa85848190813154e8a6495200 |
completed | Feb. 28, 2026, 1:23 a.m. |
Created at: Feb. 28, 2026, 1:02 a.m.