Triple
T21168946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British colonies |
E521642
|
entity |
| Predicate | beganToForm |
P133008
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [British colonies, beganToForm, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganToForm Context triple: [British colonies, beganToForm, 16th century]
-
A.
areFormedAt
chosen
Indicates that entities come into existence, are created, or take shape at a specific location, time, or context.
-
B.
began
Indicates that one entity initiated or started an action, event, or state involving another entity or context.
-
C.
onFormation
Indicates that one entity is located on or attached to the surface of a formation (such as a geological or structural feature).
-
D.
hasFormed
Indicates that an entity has come together or been created into a particular structure, group, or configuration.
-
E.
isFormedFor
Indicates that something is created, established, or brought into existence for a particular purpose, function, or beneficiary.
- 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_69e72710c73881908d41aedff8984da9 |
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.