Triple
T32741865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial High Dignitaries of the French Empire |
E837237
|
entity |
| Predicate | deFactoEndedIn |
P11097
|
FINISHED |
| Object | 1814 |
—
|
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: 1814 | Statement: [Imperial High Dignitaries of the French Empire, deFactoEndedIn, 1814]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deFactoEndedIn Context triple: [Imperial High Dignitaries of the French Empire, deFactoEndedIn, 1814]
-
A.
deFactoEndDate
chosen
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
B.
deFactoEndOfRole
Indicates the point in time when a role effectively ended in practice, regardless of any formal or official end date.
-
C.
concludedDuring
Indicates that an event, process, or state ended within the temporal bounds of another specified time period or event.
-
D.
alsoEnded
Indicates that one event or state concluded in addition to another already mentioned event or state.
-
E.
declineOrEnd
Indicates that a relationship, process, or state is either decreasing in intensity or coming to a complete end.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:12 a.m.