Triple
T33283513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Serdica |
E852115
|
entity |
| Predicate | concludedInEmpire |
P100088
|
FINISHED |
| Object | Roman Empire |
—
|
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: Roman Empire | Statement: [Treaty of Serdica, concludedInEmpire, Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concludedInEmpire Context triple: [Treaty of Serdica, concludedInEmpire, Roman Empire]
-
A.
concludedUnderEmperor
Indicates that an event, agreement, or process was completed or formally concluded during the reign of a specific emperor.
-
B.
concludedUnderRuler
Indicates that an event, agreement, or process was completed or finalized during the reign or authority of a specific ruler.
-
C.
heldInEmpire
chosen
Indicates that an event, position, or status occurred or existed within the territorial or political bounds of a particular empire.
-
D.
foundedInEmpire
Indicates that an entity (such as an organization, city, or institution) was established during the existence or rule of a specified empire.
-
E.
concludedDuringReignOf
Indicates that an event, process, or state came to an end while a particular ruler’s reign or period of authority was ongoing.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:32 a.m.