Triple
T33490835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicene party |
E857732
|
entity |
| Predicate | influencedByCouncil |
P7823
|
FINISHED |
| Object | First Council of Nicaea |
—
|
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 Nicaea | Statement: [Nicene party, influencedByCouncil, First Council of Nicaea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influencedByCouncil Context triple: [Nicene party, influencedByCouncil, First Council of Nicaea]
-
A.
councilInfluenceOn
Indicates the degree or manner in which a council affects, shapes, or exerts power over another entity or outcome.
-
B.
dominantInfluenceOnCouncil
Indicates that one entity exerts a controlling or overriding influence on the decisions or actions of a council.
-
C.
acquiredByCouncil
Indicates that something has been obtained, purchased, or taken into ownership or control by a council.
-
D.
council
Indicates that an entity serves as a governing or advisory council for another entity or within a particular domain.
-
E.
definedAtCouncil
chosen
Indicates that something was formally established, decided, or codified during a council or official deliberative meeting.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 1, 2026, 1:38 a.m.