Triple
T37825264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacob Leisler |
E943040
|
entity |
| Predicate | yearOfPosthumousReversal |
P178965
|
FINISHED |
| Object | 1695 |
—
|
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: 1695 | Statement: [Jacob Leisler, yearOfPosthumousReversal, 1695]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfPosthumousReversal Context triple: [Jacob Leisler, yearOfPosthumousReversal, 1695]
-
A.
posthumousRehabilitationYear
chosen
Indicates the year in which an individual was officially rehabilitated or cleared of charges after their death.
-
B.
repudiatedInYear
Indicates that the relationship or agreement was formally rejected, renounced, or disowned in the specified year.
-
C.
reversionYear
Indicates the year in which something returns to a previous state, condition, or ownership.
-
D.
posthumousAwardsRestoredInYear
Indicates that awards, previously revoked or unrecognized during a person’s lifetime, were officially reinstated or granted in a specified year after their death.
-
E.
secondRedenominationYear
Indicates the year in which a second redenomination event (such as a currency or unit value reset) takes place.
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: May 3, 2026, 4:19 p.m.