Triple
T28759879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III Coetus Extraordinarius Synodi Episcoporum |
E731778
|
entity |
| Predicate | convenedOutsideRegularSchedule |
P78718
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [III Coetus Extraordinarius Synodi Episcoporum, convenedOutsideRegularSchedule, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convenedOutsideRegularSchedule Context triple: [III Coetus Extraordinarius Synodi Episcoporum, convenedOutsideRegularSchedule, true]
-
A.
convenedOutside
chosen
Indicates that an event, meeting, or gathering was held in a location that is outside a specified primary or usual venue.
-
B.
convenesOn
Indicates that an event, group, or body holds a meeting or session at a specific time or date.
-
C.
convenedFor
Indicates that an event, meeting, or gathering was brought together for a specific purpose, topic, or beneficiary.
-
D.
convenesIn
Indicates that an entity brings together or assembles a group, meeting, or event at a specific place or venue.
-
E.
convenesDuring
Indicates that one entity formally gathers or brings together another entity or group during a specified time period or event.
- 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_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 6:11 a.m.