Triple
T21576702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pejepscot settlement |
E532411
|
entity |
| Predicate | partOfColonialFrontier |
P46001
|
FINISHED |
| Object | Maine frontier |
—
|
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: Maine frontier | Statement: [Pejepscot settlement, partOfColonialFrontier, Maine frontier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfColonialFrontier Context triple: [Pejepscot settlement, partOfColonialFrontier, Maine frontier]
-
A.
regionBeforeColonization
Indicates that a region is characterized or described as it existed prior to colonization by an external power.
-
B.
regionOfColonization
Indicates the geographic area or territory where a colonizing entity establishes and exercises colonial control.
-
C.
historicalFrontier
chosen
Indicates a boundary or border that historically separated two regions, territories, or spheres of influence.
-
D.
representedColony
Indicates that an entity acted as an official representative or delegate for a particular colony in some context or event.
-
E.
northernFrontier
Indicates that one entity serves as the northern boundary, edge, or frontier region relative to another entity.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9d07ddc8190a4bba08223e56f46 |
completed | April 27, 2026, 4:45 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:31 p.m.