Triple
T8384350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Synod of Bishops |
E197776
|
entity |
| Predicate | hasTypeOfAssembly |
P17334
|
FINISHED |
| Object | ordinary general assembly |
—
|
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: ordinary general assembly | Statement: [Synod of Bishops, hasTypeOfAssembly, ordinary general assembly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfAssembly Context triple: [Synod of Bishops, hasTypeOfAssembly, ordinary general assembly]
-
A.
hasAssemblyType
chosen
Indicates that an entity is associated with or classified by a specific type or method of assembly.
-
B.
hasAssembly
Indicates that an entity is composed of, or includes, one or more component parts assembled into a whole.
-
C.
hasAssembler
Indicates that one entity is responsible for assembling, putting together, or constructing another entity.
-
D.
hasTypeOfArtifact
Indicates that one entity is classified as, or belongs to, a particular type or category of artifact in relation to another entity.
-
E.
hasPackageType
Indicates that an entity is associated with or classified under a particular type or category of package.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80ded0ec81909771482e1a015a67 |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:02 p.m.