Triple
T32055733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conference of Carnuntum |
E818612
|
entity |
| Predicate | wasConvenedBy |
P173160
|
FINISHED |
| Object | Diocletian |
—
|
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: Diocletian | Statement: [Conference of Carnuntum, wasConvenedBy, Diocletian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasConvenedBy Context triple: [Conference of Carnuntum, wasConvenedBy, Diocletian]
-
A.
convenedIn
Indicates that an event, meeting, or formal gathering was brought together and held at a specific location.
-
B.
convenedFor
Indicates that an event, meeting, or gathering was brought together for a specific purpose, topic, or beneficiary.
-
C.
convenedAsPartOf
Indicates that an event, meeting, or gathering was brought together as a component or segment of a larger overarching event or process.
-
D.
convenedAfter
Indicates that one event, meeting, or gathering was formally brought together at a time later than another specified event.
-
E.
decidesToConvene
Indicates that an entity makes a decision to bring a group together for a meeting or assembly.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4efb0548190bb8f358c1623ca7d |
completed | May 3, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b267b90c8190807208cadce5ae8d |
completed | May 3, 2026, 2:26 a.m. |
Created at: May 1, 2026, 12:21 a.m.