Triple
T28017175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Pennsylvania |
E707575
|
entity |
| Predicate | beginsAs |
P12097
|
FINISHED |
| Object | proprietary colony |
—
|
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: proprietary colony | Statement: [History of Pennsylvania, beginsAs, proprietary colony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beginsAs Context triple: [History of Pennsylvania, beginsAs, proprietary colony]
-
A.
beganWith
chosen
Indicates that one event, process, or state started with or was initiated by another specified event, process, or state.
-
B.
representationBegins
Indicates that the act or state of representing something starts or comes into effect at a particular point in time.
-
C.
began
Indicates that one entity initiated or started an action, event, or state involving another entity or context.
-
D.
beganRule
Indicates that an entity started its period of ruling or governance over another entity or domain.
-
E.
preambleBeginsWith
Indicates that the preamble of a document or text starts with a specified substring, phrase, or content.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63c0796288190a5936b67d90abd00 |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:07 p.m.