Triple
T7721481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pontifical Council for Promoting the New Evangelization |
E175021
|
entity |
| Predicate | hasMottoConcept |
P33142
|
FINISHED |
| Object | new evangelization |
—
|
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: new evangelization | Statement: [Pontifical Council for Promoting the New Evangelization, hasMottoConcept, new evangelization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoConcept Context triple: [Pontifical Council for Promoting the New Evangelization, hasMottoConcept, new evangelization]
-
A.
hasMottoLikeFunction
chosen
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
-
B.
hasMottoContext
Indicates that an entity’s motto is associated with or applies within a specific contextual setting or scope.
-
C.
hasMottoInText
Indicates that an entity has a motto expressed in a specific textual form or wording.
-
D.
usesMotto
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
-
E.
hasMottoTradition
Indicates that an entity possesses a traditional motto associated with its identity or heritage.
- 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_69c6995d541c81909eaa646b1a8369a9 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7074eca4c8190bd51fd1b450729e8 |
completed | March 27, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69c7016a6cf88190b53bf4b958f0f302 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:05 p.m.