Triple
T24825205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Declaration on Christian Education |
E621166
|
entity |
| Predicate | citesSource |
P85858
|
FINISHED |
| Object | canon law on education |
—
|
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: canon law on education | Statement: [Declaration on Christian Education, citesSource, canon law on education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: citesSource Context triple: [Declaration on Christian Education, citesSource, canon law on education]
-
A.
citationOf
chosen
Indicates that one entity cites, references, or formally acknowledges another entity as a source.
-
B.
citations
Indicates that one entity references another as a source of information, evidence, or authority, typically in a scholarly or informational context.
-
C.
citesAs
Indicates that one entity references or acknowledges another as a source of information, authority, or evidence.
-
D.
citationIn
Indicates that one work cites, references, or otherwise acknowledges another work as a source.
-
E.
citesBody
Indicates that one entity references or cites the content, findings, or text of another entity as a source.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:05 a.m.