Triple
T21168984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British colonies |
E521642
|
entity |
| Predicate | involvedPolicy |
P59465
|
FINISHED |
| Object | imperialism |
—
|
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: imperialism | Statement: [British colonies, involvedPolicy, imperialism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedPolicy Context triple: [British colonies, involvedPolicy, imperialism]
-
A.
issuesPolicyOn
Indicates that an authority or organization formally creates, approves, or enacts a policy concerning a particular subject or domain.
-
B.
involvedAgreement
Indicates that an entity participates in, is a party to, or is otherwise associated with a specific agreement or contract.
-
C.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
D.
involvedAction
chosen
Indicates that an entity participates in, performs, or is otherwise engaged in a specified action or activity.
-
E.
reflectsPolicy
Indicates that one entity embodies, represents, or is aligned with the rules, principles, or stance defined by a particular policy.
- 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_69e0b50e30748190b186824a206d39b9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72711be9481909f16107b71d3500a |
completed | April 21, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3 p.m.