Triple
T36472037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Spirit as ‘Lord and giver of life’ |
E898561
|
entity |
| Predicate | clarifiedAt |
P183883
|
FINISHED |
| Object | First Council of Constantinople |
—
|
NE NERFINISHED |
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: First Council of Constantinople | Statement: [Holy Spirit as ‘Lord and giver of life’, clarifiedAt, First Council of Constantinople]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clarifiedAt Context triple: [Holy Spirit as ‘Lord and giver of life’, clarifiedAt, First Council of Constantinople]
-
A.
affirmedAt
chosen
Indicates that something has been formally confirmed, validated, or upheld at a specific time or place.
-
B.
communicatedOn
Indicates that a communication event took place on a specific date or time.
-
C.
declaredDate
Indicates the date on which something is formally announced, proclaimed, or made official.
-
D.
agreedAt
Indicates the time or point at which an agreement or consensus between parties was reached.
-
E.
concludedAt
Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.