Triple
T15004000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smederevo |
E377661
|
entity |
| Predicate | locatedInCountrySince |
P89660
|
FINISHED |
| Object | modern Serbia |
—
|
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: modern Serbia | Statement: [Smederevo, locatedInCountrySince, modern Serbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCountrySince Context triple: [Smederevo, locatedInCountrySince, modern Serbia]
-
A.
timeInCountry
Indicates the duration or amount of time that an entity spends or has spent within a particular country.
-
B.
settledInYear
Indicates the specific calendar year in which an entity became established, inhabited, or formally settled in a particular place or status.
-
C.
hostCountrySinceInception
Indicates that the referenced country has continuously served as the host location for something (e.g., an event, organization, or institution) from its very beginning.
-
D.
isLocatedInPresentDayCountry
chosen
Indicates that an entity’s location is specified in terms of the modern, currently recognized country that encompasses it.
-
E.
locationCountryAtTheTime
Indicates that an entity was located in a specified country during a particular time or time period.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7312ae48190bdaf91ecced6657e |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.