Triple
T33283536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Serdica |
E852115
|
entity |
| Predicate | modernLocationOfPlace |
P8489
|
FINISHED |
| Object | Sofia |
—
|
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: Sofia | Statement: [Treaty of Serdica, modernLocationOfPlace, Sofia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernLocationOfPlace Context triple: [Treaty of Serdica, modernLocationOfPlace, Sofia]
-
A.
modernLocationOfCity
Indicates that a historical or former city is located within the boundaries of a specified modern administrative or geographic entity.
-
B.
historicalLocationOf
Indicates that a place served as a significant site or setting for an entity during a particular historical period or event.
-
C.
historicalLocationNowIn
Indicates that an entity’s historical location is now situated within the boundaries of another, current geographic or political entity.
-
D.
modernLocality
chosen
Indicates that an entity is located in, associated with, or corresponds to a present-day geographic or administrative locality.
-
E.
modernSiteOfCapital
Indicates that the subject location is the present-day site where the capital of the object political entity is situated.
- 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_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 1, 2026, 1:32 a.m.