Triple
T14101243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kallimarmaro |
E339384
|
entity |
| Predicate | modernRestorationStartYear |
P23768
|
FINISHED |
| Object | 1869 |
—
|
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: 1869 | Statement: [Kallimarmaro, modernRestorationStartYear, 1869]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernRestorationStartYear Context triple: [Kallimarmaro, modernRestorationStartYear, 1869]
-
A.
reconstructionOrRestorationDate
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
-
B.
modernEraStart
Indicates the point in time when the modern era begins for a given subject or context.
-
C.
reconstructionYear
Indicates the year in which something was rebuilt, restored, or reconstructed after damage, alteration, or destruction.
-
D.
reconstructionStartYear
chosen
Indicates the calendar year in which a reconstruction process or project began.
-
E.
constitutionalRestorationYear
Indicates the year in which a constitution was restored or reinstated after being suspended, replaced, or otherwise not in effect.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5fbbf0b08190ba1ea3657d6db005 |
completed | April 14, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.