Triple
T28620262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CS |
E724361
|
entity |
| Predicate | successorCountryName |
P43577
|
FINISHED |
| Object | Serbia |
—
|
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: Serbia | Statement: [CS, successorCountryName, Serbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorCountryName Context triple: [CS, successorCountryName, Serbia]
-
A.
currentCountryOfSuccessor
Indicates the country in which a given successor (e.g., to a position, title, or role) is currently serving or recognized.
-
B.
countrySucceededBy
Indicates that one country is the direct successor state that replaces or follows another country in sovereignty or political continuity.
-
C.
successorCountryCode
Indicates that one country’s code represents the state that legally or historically succeeds another country’s code.
-
D.
countryAfterSuccession
chosen
Indicates that one country is the successor state that takes over from another country after a political or territorial succession.
-
E.
countryPredecessor
Indicates that one country existed before and was succeeded or replaced by another country in a historical or political sense.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: April 28, 2026, 4:33 a.m.