Triple
T16829474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Stefano |
E409109
|
entity |
| Predicate | historicalEventDateAtLocation |
P925
|
FINISHED |
| Object | 3 March 1878 |
—
|
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: 3 March 1878 | Statement: [San Stefano, historicalEventDateAtLocation, 3 March 1878]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEventDateAtLocation Context triple: [San Stefano, historicalEventDateAtLocation, 3 March 1878]
-
A.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
B.
nearHistoricalEventDate
Indicates that something occurs on a date that is close in time to a specified historical event’s date.
-
C.
notableEventDate
chosen
Indicates the date on which a notable or significant event associated with the subject occurred.
-
D.
timeOfEventCommemorated
Indicates the specific time or date at which the event being commemorated originally occurred.
-
E.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b315dbbc81908a1c83069e058770 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.