Triple
T4353593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Stephens |
E98090
|
entity |
| Predicate | endTimeAsCapital |
P55723
|
FINISHED |
| Object | 1819 |
—
|
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: 1819 | Statement: [St. Stephens, endTimeAsCapital, 1819]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTimeAsCapital Context triple: [St. Stephens, endTimeAsCapital, 1819]
-
A.
endTimeAsCaesar
Indicates the time at which an event or state ends, expressed in the Caesar (Julian) calendar time representation.
-
B.
endTimeAsCCPBase
Indicates the point in time at which an event or process concludes, expressed using the CCP base time representation.
-
C.
endTimeAsElectorPalatine
Indicates the point in time at which an entity’s role or tenure as Elector Palatine comes to an end.
-
D.
endTimeLocal
Indicates the local date and time at which an event, activity, or state concludes.
-
E.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
- 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351c281688190aef717c4ecce8107 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:15 p.m.