Triple
T38532414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian Church |
E923401
|
entity |
| Predicate | hasEarlyCouncil |
P11003
|
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: [Christian Church, hasEarlyCouncil, First Council of Nicaea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarlyCouncil Context triple: [Christian Church, hasEarlyCouncil, First Council of Nicaea]
-
A.
hadElectedCouncil
Indicates that an entity was governed or administered by a council whose members were chosen through an election process.
-
B.
hasCouncilStructure
Indicates that an entity is organized or governed according to a specific council-based structure or system.
-
C.
heldCouncil
chosen
Indicates that an entity organized and conducted a formal meeting or assembly for discussion or decision-making with other participants.
-
D.
hasCouncilFire
Indicates that an entity maintains or participates in a central gathering or decision-making assembly symbolized by a council fire.
-
E.
hasOrderInCouncil
Indicates that an entity is associated with, or governed by, a specific Order in Council (a formal executive decision or regulation).
- 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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.