Triple
T16059470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chisan-ha |
E389567
|
entity |
| Predicate | hasDoctrinalElement |
P33315
|
FINISHED |
| Object | three mysteries doctrine |
—
|
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: three mysteries doctrine | Statement: [Chisan-ha, hasDoctrinalElement, three mysteries doctrine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDoctrinalElement Context triple: [Chisan-ha, hasDoctrinalElement, three mysteries doctrine]
-
A.
hasDoctrinalCharacteristic
chosen
Indicates that an entity possesses a specific doctrinal feature, quality, or attribute within a belief or teaching system.
-
B.
hasDoctrinalStandardInPart
Indicates that one entity possesses or upholds a specific doctrinal standard within a particular section or component of itself.
-
C.
hasDoctrinalBasis
Indicates that one concept, claim, or practice is grounded in, supported by, or derived from a specific doctrine or set of doctrines.
-
D.
hasNumberOfDoctrines
Indicates the relationship that specifies how many doctrines are associated with a given entity.
-
E.
hasDoctrinalImplication
Indicates that one concept, statement, or action carries consequences or significance for a system of beliefs, teachings, or doctrines.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.