Triple
T31339622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cartennae |
E799268
|
entity |
| Predicate | modernCountrySuccessor |
P13840
|
FINISHED |
| Object | Algeria |
—
|
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: Algeria | Statement: [Cartennae, modernCountrySuccessor, Algeria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernCountrySuccessor Context triple: [Cartennae, modernCountrySuccessor, Algeria]
-
A.
currentCountryOfSuccessor
Indicates the country in which a given successor (e.g., to a position, title, or role) is currently serving or recognized.
-
B.
countrySuccessor
chosen
Indicates that one country is the direct successor state to another, inheriting its sovereignty or international status.
-
C.
successorInCountry
Indicates that one entity takes over a role, position, or function from another entity within the same country.
-
D.
countryPredecessor
Indicates that one country existed before and was succeeded or replaced by another country in a historical or political sense.
-
E.
successorSovereign
Indicates that one entity becomes the next ruling sovereign following another entity, inheriting their position of supreme authority.
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 29, 2026, 9:16 p.m.