Triple
T5412775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donation of Constantine |
E121050
|
entity |
| Predicate | assertsDoctrine |
P14528
|
FINISHED |
| Object | supremacy of the Roman Church |
—
|
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: supremacy of the Roman Church | Statement: [Donation of Constantine, assertsDoctrine, supremacy of the Roman Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assertsDoctrine Context triple: [Donation of Constantine, assertsDoctrine, supremacy of the Roman Church]
-
A.
containsDoctrine
Indicates that one entity includes, embodies, or incorporates the doctrine, principles, or teachings represented by another entity.
-
B.
usesDoctrine
Indicates that one entity applies, follows, or relies on a particular doctrine in its actions or reasoning.
-
C.
confirmedDoctrine
chosen
Indicates that an authority has officially validated, endorsed, or ratified a particular doctrine as true or acceptable.
-
D.
createdDoctrine
Indicates that an entity originated, formulated, or established a particular doctrine, theory, or set of principles.
-
E.
concernsDoctrine
Indicates that something is related or pertains specifically to a particular doctrine or set of doctrinal principles.
- 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87bb3c0c81908711784bc865ff03 |
completed | March 20, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.