Triple
T7648547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhode Island's 1st congressional district |
E173186
|
entity |
| Predicate | hasCoastalAreas |
P1896
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Rhode Island's 1st congressional district, hasCoastalAreas, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalAreas Context triple: [Rhode Island's 1st congressional district, hasCoastalAreas, true]
-
A.
hasCoastalRegion
Indicates that a place possesses at least one region that borders or is directly adjacent to a sea or ocean.
-
B.
hasCoastalAdjacentArea
Indicates that one area directly borders or is immediately next to a coastal zone.
-
C.
hasCoastalDistrict
Indicates that an administrative region or area includes at least one district that borders a sea or ocean.
-
D.
hasCoastline
chosen
Indicates that a geographic entity is bordered by and directly touches a sea or ocean along part of its boundary.
-
E.
hasCoastalMunicipalities
Indicates that a region or higher-level area includes one or more municipalities that are located along a sea or ocean coastline.
- 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_69c6995473348190a4f41d110d619a18 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c6fb134a40819097f9de5f24d1df0f |
completed | March 27, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e9ef1c81909c8bff716541ac1f |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:58 p.m.