Triple
T37585130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Crescent Township, Houston County, Minnesota |
E935080
|
entity |
| Predicate | bordersOrIsAdjacentTo |
P5707
|
FINISHED |
| Object | City of La Crescent, Minnesota |
—
|
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: City of La Crescent, Minnesota | Statement: [La Crescent Township, Houston County, Minnesota, bordersOrIsAdjacentTo, City of La Crescent, Minnesota]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bordersOrIsAdjacentTo Context triple: [La Crescent Township, Houston County, Minnesota, bordersOrIsAdjacentTo, City of La Crescent, Minnesota]
-
A.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
B.
isAdjacentTo
chosen
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
-
C.
hasBorderRelation
Indicates that one entity shares a boundary or border with another entity.
-
D.
geographicallyBorders
Indicates that two geographic entities share a common boundary or border.
-
E.
connectsToCountryBorder
Indicates that one entity is directly adjacent to and touches the border of a specified country.
- 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0010e46d948190a51111b5270fade7 |
completed | May 10, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_6a001061d34c8190bfe73f3d7c061eb7 |
completed | May 10, 2026, 4:58 a.m. |
Created at: May 3, 2026, 4:17 p.m.