Triple
T20991124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apostolic Tradition |
E517024
|
entity |
| Predicate | isImportantSourceFor |
P1887
|
FINISHED |
| Object | history of early Christian liturgy |
—
|
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: history of early Christian liturgy | Statement: [Apostolic Tradition, isImportantSourceFor, history of early Christian liturgy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isImportantSourceFor Context triple: [Apostolic Tradition, isImportantSourceFor, history of early Christian liturgy]
-
A.
isImportantFor
chosen
Indicates that something holds significant value, relevance, or necessity in relation to something else.
-
B.
isOfficialSourceFor
Indicates that one entity is recognized as an authoritative or formally sanctioned provider of information or content about another entity.
-
C.
isMajorSourceOf
Indicates that one entity serves as a primary or dominant origin, cause, or provider of another entity or effect.
-
D.
containsSourceOf
Indicates that one entity includes, holds, or encompasses the origin or cause of another entity.
-
E.
usesSigningSource
Indicates that one entity performs signing operations by relying on another specified source or mechanism for the signing process.
- 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.