Triple
T6426169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Jordan |
E128062
|
entity |
| Predicate | renamedWithCountry |
P52429
|
FINISHED |
| Object | 1949 |
—
|
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: 1949 | Statement: [King of Jordan, renamedWithCountry, 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renamedWithCountry Context triple: [King of Jordan, renamedWithCountry, 1949]
-
A.
replacedInCountry
Indicates that one entity has been substituted or superseded by another within the context or jurisdiction of a specific country.
-
B.
countryAfterReplacement
Indicates that one country takes the place of another as a successor or replacement in a given context or role.
-
C.
usedNameOfCountry
Indicates that one entity referred to or employed a particular name or designation for a country.
-
D.
convertedCountryTo
Indicates that an entity has changed or transformed another entity into a specified country or country-level status.
-
E.
renamedTerritory
chosen
Indicates that an existing territory has been given a new official name, linking the former designation to its updated one.
- 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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0691f944c81909d4e5d8ef9e494b6 |
completed | March 22, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69c060f780b08190aa650b4d1fc51f21 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:43 p.m.