Triple
T790873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Dominions |
E16909
|
entity |
| Predicate | supersededByTerm |
P14487
|
FINISHED |
| Object | Commonwealth country |
—
|
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: Commonwealth country | Statement: [British Dominions, supersededByTerm, Commonwealth country]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supersededByTerm Context triple: [British Dominions, supersededByTerm, Commonwealth country]
-
A.
wasSupersededBy
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
B.
supersededInPrecisionBy
Indicates that one entity’s level of precision has been replaced or overtaken by another entity’s greater precision.
-
C.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
D.
cededFrom
Indicates that control, ownership, or sovereignty over something was transferred away from a source entity to another entity, typically through a formal or legal act of cession.
-
E.
successorCategory
chosen
Indicates that one category directly follows or replaces another in an ordered sequence or hierarchy.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a79754988190ab494b1c54d6a2a4 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50ef72c819084ffe9f31dbd0262 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:38 p.m.