Triple
T28759869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III Coetus Extraordinarius Synodi Episcoporum |
E731778
|
entity |
| Predicate | heldWithin |
P46132
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [III Coetus Extraordinarius Synodi Episcoporum, heldWithin, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldWithin Context triple: [III Coetus Extraordinarius Synodi Episcoporum, heldWithin, 20th century]
-
A.
heldAlong
Indicates that one entity is held or supported in a position that follows or runs parallel to the length or course of another entity.
-
B.
heldAs
Indicates that one entity is kept, maintained, or regarded in a particular state, role, or condition by another entity.
-
C.
containedWith
chosen
Indicates that one entity is located or kept inside the bounds or interior space of another entity.
-
D.
held
Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
-
E.
formedWithin
Indicates that one entity was created, established, or came into existence inside the spatial or structural bounds of another entity.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:11 a.m.