Triple
T2969696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papacy |
E80250
|
entity |
| Predicate | foundedOnBeliefIn |
P38879
|
FINISHED |
| Object | primacy of Saint Peter |
—
|
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: primacy of Saint Peter | Statement: [Papacy, foundedOnBeliefIn, primacy of Saint Peter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedOnBeliefIn Context triple: [Papacy, foundedOnBeliefIn, primacy of Saint Peter]
-
A.
foundedReligion
Indicates that an entity established or originated a particular religion.
-
B.
religiousAffiliationAtFoundation
Indicates the religious denomination or tradition with which an entity was affiliated at the time it was founded.
-
C.
basedOnBelief
chosen
Indicates that one entity’s action, decision, or assertion is grounded in, motivated by, or derived from a particular belief held by that entity.
-
D.
religiousMotivation
Indicates that an action, decision, or relationship is driven or significantly influenced by religious beliefs, values, or obligations.
-
E.
foundedAsResultOf
Indicates that one entity was established or created as a direct consequence or outcome of another event, action, or circumstance.
- 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_69ad8b14ffe881908ffed62f9595c867 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad997282b481909d078be0e70d9930 |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960e71f8819088179d11248c6ed0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.