Triple
T35599694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudo Polje |
E1028731
|
entity |
| Predicate | hasCountryAtTimeOfName |
P878
|
FINISHED |
| Object | Serbia |
E26132
|
NE 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: Serbia | Statement: [Rudo Polje, hasCountryAtTimeOfName, Serbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountryAtTimeOfName Context triple: [Rudo Polje, hasCountryAtTimeOfName, Serbia]
-
A.
countryAtTheTime
chosen
Indicates that an entity is associated with a specific country as it existed at a particular point in time.
-
B.
existedBeforeCountryNameChange
Indicates that an entity existed prior to the point in time when a country changed its official name.
-
C.
projectCountryAtTheTime
Indicates the country with which a project was associated at the specific time or period in question.
-
D.
historicallyAssociatedWithModernCountry
Indicates that an entity has a significant historical connection, influence, or origin related to a specified modern country.
-
E.
countryDuringNameUsage
Indicates the country in which a particular name was in use during a specified time period.
- F. None of above.
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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a387273f5888190acb5590f1e2c9a73 |
completed | June 21, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.