Triple
T2312505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Head of Doctrine |
E51989
|
entity |
| Predicate | canonicalOrderInCanonsOfDort |
P28463
|
FINISHED |
| Object | Second Head |
—
|
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: Second Head | Statement: [Second Head of Doctrine, canonicalOrderInCanonsOfDort, Second Head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalOrderInCanonsOfDort Context triple: [Second Head of Doctrine, canonicalOrderInCanonsOfDort, Second Head]
-
A.
inChristianCanonOrder
Indicates that the entities are arranged according to the sequence used in the Christian biblical canon.
-
B.
canonizedIn
Indicates that an authority formally declared someone to be a saint or holy figure in a specified place or institution.
-
C.
canonizedBy
Indicates that an entity has been officially declared a saint or holy figure by a specified religious authority.
-
D.
canonizedAs
Indicates that an authority, typically a religious institution, has formally declared someone to be a saint or holy figure.
-
E.
scripturalOrder
chosen
Indicates that one entity precedes another according to the sequence or arrangement prescribed in a scriptural or sacred text.
- 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc58e88e481908733fdf79d3f8a15 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.