Triple
T33485868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Cardinal Krol |
E857608
|
entity |
| Predicate | endTimeForPreviousPost |
P100319
|
FINISHED |
| Object | 1961 |
—
|
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: 1961 | Statement: [John Cardinal Krol, endTimeForPreviousPost, 1961]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTimeForPreviousPost Context triple: [John Cardinal Krol, endTimeForPreviousPost, 1961]
-
A.
previousPostEndDate
chosen
Indicates the date on which the immediately preceding post, position, or assignment ended.
-
B.
timePeriodAfter
Indicates that one time period occurs entirely later than another time period in a temporal sequence.
-
C.
endTimeAsMP
Indicates the time at which an event or state concludes, expressed in minutes past midnight.
-
D.
endTimeAsCapital
Indicates that a specified time marks the ending point of an event, process, or state in the role of its designated capital or primary endpoint.
-
E.
latestTime
Indicates the most recent point in time at which the related event, state, or condition occurs or is valid among a set of possible times.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: May 1, 2026, 1:38 a.m.