Triple
T36838701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penobscot Indian Island community |
E910344
|
entity |
| Predicate | riverIslandCommunityOn |
P156002
|
FINISHED |
| Object | Penobscot River |
—
|
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: Penobscot River | Statement: [Penobscot Indian Island community, riverIslandCommunityOn, Penobscot River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverIslandCommunityOn Context triple: [Penobscot Indian Island community, riverIslandCommunityOn, Penobscot River]
-
A.
riverIslandSettlement
Indicates a settlement that is located on an island within a river.
-
B.
isIslandCommunityCenter
Indicates that a location functions as the primary communal hub or gathering place for an island community.
-
C.
isIslandCommunity
Indicates that a community is located on an island and is geographically separated from mainland areas.
-
D.
isOnRiverIsland
chosen
Indicates that one entity (typically a place or structure) is located on an island situated within a river.
-
E.
engagedOnIsland
Indicates that two or more entities became engaged (e.g., to be married or formally committed) while they were on an island.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:13 p.m.