Triple
T10335314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Sirmium |
E242986
|
entity |
| Predicate | numberOfSynods |
P93754
|
FINISHED |
| Object | multiple synods |
—
|
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: multiple synods | Statement: [Council of Sirmium, numberOfSynods, multiple synods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfSynods Context triple: [Council of Sirmium, numberOfSynods, multiple synods]
-
A.
hasSynod
Indicates that an entity is associated with, governed by, or participates in a particular synod (a formal ecclesiastical council or assembly).
-
B.
hasSynodMembers
Indicates that a synod includes or is composed of the specified members.
-
C.
typeOfSynod
Indicates the specific kind or category to which a particular synod belongs.
-
D.
relatedSynod
Indicates a relationship where one entity is associated with, connected to, or involved in the same synod (a formal ecclesiastical council or assembly) as another entity.
-
E.
synodPurpose
Indicates that a synod is convened or exists for a particular purpose, goal, or intended function.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e91fdb2081909866c6ecf417d75a |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 11:53 a.m.