Triple
T27201147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pontifical Council for Promoting the New Evangelization |
E683738
|
entity |
| Predicate | effectiveStartYear |
P10338
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Pontifical Council for Promoting the New Evangelization, effectiveStartYear, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveStartYear Context triple: [Pontifical Council for Promoting the New Evangelization, effectiveStartYear, 2010]
-
A.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
B.
effectivePeriodStart
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
-
C.
effectiveForAnnualPeriodsBeginningOnOrAfter
Indicates that something (such as a rule, standard, or requirement) applies starting from annual reporting periods whose first day is on or after a specified date.
-
D.
eligibilityPeriodStartYear
Indicates the calendar year in which an entity’s eligibility period begins.
-
E.
beganInYear
chosen
Indicates that an event, process, or state started in a specific calendar year.
- 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_69eefad1fd5c8190a4a46ea6afe58bfa |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 27, 2026, 9:36 a.m.