Triple
T782440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Trinity |
E16526
|
entity |
| Predicate | developedThrough |
P19846
|
FINISHED |
| Object | Christological controversies |
—
|
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: Christological controversies | Statement: [Holy Trinity, developedThrough, Christological controversies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedThrough Context triple: [Holy Trinity, developedThrough, Christological controversies]
-
A.
developed
Indicates that one entity created, designed, or brought another entity into a more advanced or complete state through effort or work.
-
B.
developedAlong
Indicates that something was created, constructed, or evolved following the course, path, or boundary of something else.
-
C.
developedAs
Indicates that one entity was created, designed, or evolved specifically to function as or replace another entity.
-
D.
developedUnder
Indicates that something was created, produced, or brought into existence while being subject to the authority, guidance, or conditions imposed by a particular person, organization, regime, or framework.
-
E.
developedFrom
Indicates that one entity originates, evolves, or is derived from another as its source or precursor.
- F. None of above. chosen
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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a90365648190ace53b0f0e87aa68 |
completed | March 1, 2026, 9 p.m. |
| PD | Predicate disambiguation | batch_69a4a50bd23081908908235b8ec9201e |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a8f09d108190b8c83a6169d65c0c |
completed | March 1, 2026, 9 p.m. |
Created at: March 1, 2026, 7:37 p.m.