Triple
T29624766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illinois–Wisconsin border |
E755106
|
entity |
| Predicate | easternTerminusBodyOfWater |
P77370
|
FINISHED |
| Object | Lake Michigan |
—
|
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: Lake Michigan | Statement: [Illinois–Wisconsin border, easternTerminusBodyOfWater, Lake Michigan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: easternTerminusBodyOfWater Context triple: [Illinois–Wisconsin border, easternTerminusBodyOfWater, Lake Michigan]
-
A.
waterBodyOnEast
Indicates that one water body is located to the east of another water body.
-
B.
hasBodyOfWaterOnEast
chosen
Indicates that a place or region has a body of water located directly to its east.
-
C.
河口の海域
Indicates a spatial relationship where something is located in, occurs in, or is associated with the marine area at or near a river mouth.
-
D.
соединяетМоре
Indicates that one entity connects or links a sea to another geographic feature or body of water.
-
E.
locatedOnEasternShoreOf
Indicates that one entity is situated on the eastern shore or bank of another geographic feature, such as a body of water or landform.
- 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66e5f7e30819094530abceabd5f43 |
completed | May 2, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:37 p.m.