Triple
T20991113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apostolic Tradition |
E517024
|
entity |
| Predicate | documentsPracticeOf |
P82572
|
FINISHED |
| Object | ordination of bishops |
—
|
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: ordination of bishops | Statement: [Apostolic Tradition, documentsPracticeOf, ordination of bishops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentsPracticeOf Context triple: [Apostolic Tradition, documentsPracticeOf, ordination of bishops]
-
A.
documentsCommunity
Indicates that an entity records, describes, or provides information about a particular community.
-
B.
publicPractice
Indicates that an activity, behavior, or belief is carried out openly in public or within a community setting rather than privately.
-
C.
documentsPerspective
Indicates that one entity records, represents, or expresses the viewpoint or perspective of another entity.
-
D.
documentsActivity
chosen
Indicates that one entity records, describes, or provides evidence of an activity performed by another entity.
-
E.
documentsNow
Indicates that an entity is currently documenting, recording, or writing about another entity at the present time.
- 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc1ba3d0819080d9d03817a45026 |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:50 p.m.