Triple
T2782767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lincoln Home National Historic Site |
E61734
|
entity |
| Predicate | periodOfSignificanceStart |
P39608
|
FINISHED |
| Object | 1844 |
—
|
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: 1844 | Statement: [Lincoln Home National Historic Site, periodOfSignificanceStart, 1844]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfSignificanceStart Context triple: [Lincoln Home National Historic Site, periodOfSignificanceStart, 1844]
-
A.
beganInYear
Indicates that an event, process, or state started in a specific calendar year.
-
B.
notableEraStart
chosen
Indicates the point in time when a notable or historically significant era associated with an entity begins.
-
C.
approximateStartYear
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
-
D.
historicalPeriodOfSignificance
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
-
E.
historicalMigrationPeriodStart
Indicates the point in time when a particular historical migration period begins.
- 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_69ab4b7e43c48190997b8fc8fb1663ab |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdd00b65c8190a8ea444308c4fa2b |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.