Triple
T4521002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Christopher |
E103267
|
entity |
| Predicate | reasonForCalendarChange |
P5019
|
FINISHED |
| Object | historicity considered uncertain |
—
|
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: historicity considered uncertain | Statement: [Saint Christopher, reasonForCalendarChange, historicity considered uncertain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForCalendarChange Context triple: [Saint Christopher, reasonForCalendarChange, historicity considered uncertain]
-
A.
reasonForChange
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
B.
changeReason
chosen
Indicates the reason or justification for a modification or change made to an entity or its state.
-
C.
reasonForTime
Indicates that one entity provides the explanation or cause for a particular point or duration of time associated with another entity.
-
D.
reasonForEvent
Indicates that one event occurs as a consequence of, or is motivated or explained by, another specified cause or reason.
-
E.
startDateChangedTo
Indicates that the start date of something has been modified from its previous value to a new specified date.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5749d95481908db0176459c096cf |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521cf77c819083852de3094d1377 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:02 p.m.