Triple
T32289399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jubilee in the Catholic Church |
E824921
|
entity |
| Predicate | typicalIntervalYears |
P84192
|
FINISHED |
| Object | 25 |
—
|
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: 25 | Statement: [Jubilee in the Catholic Church, typicalIntervalYears, 25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalIntervalYears Context triple: [Jubilee in the Catholic Church, typicalIntervalYears, 25]
-
A.
typicalExampleInterval
Indicates the characteristic or most representative time span during which an associated event, state, or condition typically occurs.
-
B.
typicalPeriodRange
Indicates the usual or most commonly observed range of time intervals associated with an event, process, or state.
-
C.
durationInYears
Indicates the length of time associated with something, measured in whole or fractional years.
-
D.
appliesInYears
Indicates that something (such as a rule, condition, or effect) is valid, relevant, or in force during specific years.
-
E.
typicalPeriod
chosen
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:44 a.m.