Triple
T789884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dominions of the British Empire |
E16887
|
entity |
| Predicate | differedFrom |
P1612
|
FINISHED |
| Object | Crown colonies |
—
|
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: Crown colonies | Statement: [Dominions of the British Empire, differedFrom, Crown colonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: differedFrom Context triple: [Dominions of the British Empire, differedFrom, Crown colonies]
-
A.
differentiatedFrom
Indicates that one entity is distinguished or set apart from another by identifying differences between them.
-
B.
isDistinctFrom
chosen
Indicates that two entities are not identical and can be clearly distinguished from one another.
-
C.
hasGrammarDifferenceFrom
Indicates that two linguistic items differ from each other in their grammatical form, structure, or rules of usage.
-
D.
formsDeltaWith
Indicates that one entity combines or interacts with another to produce a change or difference (a “delta”) between states, values, or conditions.
-
E.
oftenContrastedWith
Indicates that one entity is frequently compared to another in a way that highlights their differences or opposing characteristics.
- 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_69a4a7841b0c8190859ecd247e32c6ec |
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.