Triple
T28620260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CS |
E724361
|
entity |
| Predicate | successorCountryCode |
P194353
|
FINISHED |
| Object | RS |
—
|
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: RS | Statement: [CS, successorCountryCode, RS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorCountryCode Context triple: [CS, successorCountryCode, RS]
-
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.
successorCurrencyCountry
Indicates that one country’s currency has replaced another country’s currency as the official or primary monetary unit in use.
-
D.
countryAfterSuccession
Indicates that one country is the successor state that takes over from another country after a political or territorial succession.
-
E.
successorInCountry
Indicates that one entity takes over a role, position, or function from another entity within the same country.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
| PDg | Predicate description generation | batch_69fd6dbc3ac0819093fbcfe95f12b93d |
completed | May 8, 2026, 4:59 a.m. |
Created at: April 28, 2026, 4:33 a.m.