Triple
T27510544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mageik |
E694395
|
entity |
| Predicate | isRelatedToGeographicRegion |
P146651
|
FINISHED |
| Object | Alaska Peninsula |
—
|
NE NERFINISHED |
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: Alaska Peninsula | Statement: [Mageik, isRelatedToGeographicRegion, Alaska Peninsula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRelatedToGeographicRegion Context triple: [Mageik, isRelatedToGeographicRegion, Alaska Peninsula]
-
A.
geographicalRegionType
Indicates the specific kind or category of geographical region that an entity belongs to (e.g., continent, country, province, or city).
-
B.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
C.
hasGeographicConnectionTo
chosen
Indicates a relationship where two entities are linked through a shared or relevant geographic feature, location, or spatial association.
-
D.
regionallyAssociatedWith
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
-
E.
isRegion
Indicates that one entity functions as a geographic or administrative region associated with 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 1:15 p.m.