Triple
T8873191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan |
E211208
|
entity |
| Predicate | hasExtensiveFreshwaterCoastline |
P85464
|
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: [Michigan, hasExtensiveFreshwaterCoastline, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExtensiveFreshwaterCoastline Context triple: [Michigan, hasExtensiveFreshwaterCoastline, true]
-
A.
hasCoastline
Indicates that a geographic entity is bordered by and directly touches a sea or ocean along part of its boundary.
-
B.
hasCoastlineOn
Indicates that one entity’s coastline borders or is directly adjacent to a specified body of water.
-
C.
hasMainlandCoastline
Indicates that a geographic entity possesses a coastline that is directly connected to a continental mainland, rather than only to islands or inland bodies of water.
-
D.
hasCoastalRegion
Indicates that a place possesses at least one region that borders or is directly adjacent to a sea or ocean.
-
E.
influencedCoastlineOf
Indicates that one entity has affected, shaped, or altered the characteristics, form, or condition of another entity’s coastline.
- F. None of above. chosen
Provenance (4 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_69ca838e78748190934d82db3104f855 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc612952348190856d6964122c3f01 |
completed | April 1, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5d6e54808190af4156edd4c8ffbc |
completed | March 31, 2026, 11:49 p.m. |
Created at: March 30, 2026, 6:52 p.m.