Triple
T37857648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CUKC |
E944234
|
entity |
| Predicate | succeededInUKBy |
P120984
|
FINISHED |
| Object | right of abode concept |
—
|
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: right of abode concept | Statement: [CUKC, succeededInUKBy, right of abode concept]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededInUKBy Context triple: [CUKC, succeededInUKBy, right of abode concept]
-
A.
successorInUK
Indicates that one entity directly follows another in a succession specific to the United Kingdom, such as in an official role, title, or office.
-
B.
succeededInCountryBy
chosen
Indicates that an entity holding a position, role, or status in a specific country is followed or replaced by another entity in that same country.
-
C.
statusInUK
Indicates the legal or official status that an entity holds within the United Kingdom (e.g., immigration, residency, or authorization category).
-
D.
succeededByInHolland
Indicates that one entity is directly followed or replaced by another entity in a succession specific to Holland.
-
E.
succeededByAsAmbassadorToUK
Indicates that one entity later took over the role of ambassador to the UK from another entity.
- 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00bc079314819096271bba60bee52d |
completed | May 10, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_6a00bba5bd408190ace5db0c4a90dc6f |
completed | May 10, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4:19 p.m.