Triple
T27899710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brookfield, Wisconsin |
E705593
|
entity |
| Predicate | distanceToMilwaukeeDowntown |
P24901
|
FINISHED |
| Object | approximately 10 miles west |
—
|
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: approximately 10 miles west | Statement: [Brookfield, Wisconsin, distanceToMilwaukeeDowntown, approximately 10 miles west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMilwaukeeDowntown Context triple: [Brookfield, Wisconsin, distanceToMilwaukeeDowntown, approximately 10 miles west]
-
A.
distanceToMilwaukee
chosen
Indicates the measured or calculated spatial distance between a given entity’s location and the city of Milwaukee.
-
B.
distanceToMadison
Indicates the spatial distance between a given entity and the location identified as Madison.
-
C.
distanceToGrandRapidsDowntown
Indicates the physical distance between a given location and downtown Grand Rapids.
-
D.
distanceToGreenBay
Indicates the measured distance between a given entity’s location and the location of Green Bay.
-
E.
directionFromMilwaukee
Indicates the relative compass direction of one place or object as measured outward starting from Milwaukee.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69ff9bed58dc8190a204816d4ed6c32c |
completed | May 9, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69ff9b69653c81908ab0d88055a66a88 |
completed | May 9, 2026, 8:39 p.m. |
Created at: April 27, 2026, 6:41 p.m.