Triple
T34860572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Creed of Antioch |
E1004857
|
entity |
| Predicate | relatedToCreed |
P69470
|
FINISHED |
| Object | Nicene Creed |
E940
|
NE 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: Nicene Creed | Statement: [Third Creed of Antioch, relatedToCreed, Nicene Creed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToCreed Context triple: [Third Creed of Antioch, relatedToCreed, Nicene Creed]
-
A.
relationToOtherCreeds
Indicates how one belief system, doctrine, or creed is positioned or related in comparison to other creeds.
-
B.
relatedBelief
chosen
Indicates that one belief is connected to, derived from, or otherwise associated with another belief in some meaningful way.
-
C.
relatedCovenant
Indicates a relationship in which one covenant is connected to, associated with, or derived from another covenant.
-
D.
supportedCreed
Indicates that one entity endorsed, upheld, or actively promoted a particular belief system, doctrine, or set of principles associated with another entity.
-
E.
associatedReligionOrBelief
Indicates that an entity is connected to, identified with, or characterized by a particular religion or belief system.
- F. None of above.
Provenance (4 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37795ca3408190a89af6b177cba73f |
completed | June 21, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.