Triple
T9775390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bay of Islands |
E237232
|
entity |
| Predicate | wasEarlyContactZoneFor |
P6793
|
FINISHED |
| Object | European explorers |
—
|
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: European explorers | Statement: [Bay of Islands, wasEarlyContactZoneFor, European explorers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasEarlyContactZoneFor Context triple: [Bay of Islands, wasEarlyContactZoneFor, European explorers]
-
A.
wasFrontierBetween
Indicates that one entity historically served as the boundary or border region separating two other entities.
-
B.
hasZone
chosen
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
C.
formerZone
Indicates that an entity was previously designated as a particular zone or area but no longer holds that status.
-
D.
wasFrontierRegion
Indicates that a region historically functioned as a frontier area, marking a boundary or border zone between larger political or cultural entities.
-
E.
hasHistoricalRegionOverlap
Indicates that two historical regions share a common geographic area or have partially overlapping territorial extents during a given time period.
- 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_69ca84d975a08190aab25b02a89bdab3 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda1325a988190a07a3dc4dce41cb3 |
completed | April 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:26 p.m.