Triple
T27482982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Brookfield, Wisconsin |
E693651
|
entity |
| Predicate | regionallyNearby |
P61362
|
FINISHED |
| Object | City of Milwaukee, Wisconsin |
—
|
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 Milwaukee, Wisconsin | Statement: [City of Brookfield, Wisconsin, regionallyNearby, City of Milwaukee, Wisconsin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionallyNearby Context triple: [City of Brookfield, Wisconsin, regionallyNearby, City of Milwaukee, Wisconsin]
-
A.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
-
B.
nearbyRegionCharacterizedBy
Indicates that a region located nearby another entity is defined or distinguished by a particular characteristic, feature, or condition.
-
C.
nearbySettlementRegion
Indicates that a settlement is located close to or within the surrounding area of a specified region.
-
D.
nearbyTo
chosen
Indicates that one entity is located close in distance or position to another entity.
-
E.
featuresRegionalProximity
Indicates that one entity is located near or in close geographic proximity to a particular region or another entity.
- 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 27, 2026, 1 p.m.