Triple
T33283512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Serdica |
E852115
|
entity |
| Predicate | concludedInProvince |
P177007
|
FINISHED |
| Object | Roman province of Thracia |
—
|
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 province of Thracia | Statement: [Treaty of Serdica, concludedInProvince, Roman province of Thracia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concludedInProvince Context triple: [Treaty of Serdica, concludedInProvince, Roman province of Thracia]
-
A.
heldInProvince
Indicates that an event or activity takes place within the boundaries of a specified province.
-
B.
stationedInProvince
Indicates that an entity is assigned or based in a particular province as its location or area of operation.
-
C.
isInProvince
Indicates that one entity (typically a place or city) is located within the administrative boundaries of a specified province.
-
D.
concentratedInProvince
Indicates that something is primarily located, focused, or densely present within a particular province.
-
E.
endProvince
Indicates that an entity marks the boundary or final extent of a province within a larger territorial or administrative structure.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f814fcf48190ae4504154d1b2c05 |
completed | May 3, 2026, 7:24 a.m. |
Created at: May 1, 2026, 1:32 a.m.