Triple
T11320552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brownsville Township, Minnesota |
E268081
|
entity |
| Predicate | isIncorporatedArea |
P19845
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Brownsville Township, Minnesota, isIncorporatedArea, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIncorporatedArea Context triple: [Brownsville Township, Minnesota, isIncorporatedArea, false]
-
A.
isIncorporatedPlace
chosen
Indicates that a location is a legally established, self-governing municipal entity (such as a city, town, or village) recognized as an incorporated place.
-
B.
isInArea
Indicates that one entity is located within the spatial bounds or region defined by another entity.
-
C.
isPartOfCombinedArea
Indicates that an entity belongs to or is included within a larger merged or aggregated area.
-
D.
isInSubregion
Indicates that one region or area is located within the boundaries of another, more specific subregion.
-
E.
isLocatedInAdministrativeArea
Indicates that one entity is situated within the geographic or jurisdictional boundaries of a specified administrative area (such as a city, county, state, or region).
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9de875481908acfa56015d4b46f |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.