Triple
T32178629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3M Open |
E821922
|
entity |
| Predicate | locationRelativeToMajorCity |
P203848
|
FINISHED |
| Object | north of Minneapolis–Saint Paul |
—
|
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: north of Minneapolis–Saint Paul | Statement: [3M Open, locationRelativeToMajorCity, north of Minneapolis–Saint Paul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationRelativeToMajorCity Context triple: [3M Open, locationRelativeToMajorCity, north of Minneapolis–Saint Paul]
-
A.
locationRelativeToLargestCity
Indicates how a place is spatially positioned or oriented in relation to the largest city in a given area or region.
-
B.
distanceFromMajorCity
Indicates the measured distance between a given location and a specified major city.
-
C.
cityLocation
Indicates that a city is geographically situated within or associated with a specific larger area or place.
-
D.
nearestMajorCity
Indicates that one city is the closest significant urban center to another location or city compared to all other major cities.
-
E.
hasRelativePositionInCity
Indicates that one entity occupies a specific spatial or positional relationship within the boundaries or layout of a particular city.
- F. None of above. chosen
Provenance (4 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a022348ae2881908eae1be79b6f6ff6 |
completed | May 11, 2026, 6:43 p.m. |
| PD | Predicate disambiguation | batch_6a0220beb6b08190981fb86363757517 |
completed | May 11, 2026, 6:32 p.m. |
| PDg | Predicate description generation | batch_6a0223480ba08190bcde952a61fc4641 |
completed | May 11, 2026, 6:43 p.m. |
Created at: May 1, 2026, 12:34 a.m.