Triple
T8851377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cedarburg, Wisconsin |
E210645
|
entity |
| Predicate | distanceFromMilwaukee |
P24901
|
FINISHED |
| Object | approximately 20 miles north |
—
|
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 20 miles north | Statement: [Cedarburg, Wisconsin, distanceFromMilwaukee, approximately 20 miles north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromMilwaukee Context triple: [Cedarburg, Wisconsin, distanceFromMilwaukee, approximately 20 miles north]
-
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.
distanceToGreenBay
Indicates the measured distance between a given entity’s location and the location of Green Bay.
-
D.
distanceToDetroit
Indicates the measured or calculated spatial distance between a given entity and the location of Detroit.
-
E.
distanceFromDesMoines
Indicates the physical distance between a given location and the city of Des Moines.
- 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_69ca838a424c8190b1ecac115c2927e7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60c2300c819097b1ca6ebe2f749a |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:49 p.m.