Triple
T23944455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota Mining and Manufacturing Company |
E602875
|
entity |
| Predicate | headquartersLocationCity |
P60125
|
FINISHED |
| Object | Saint Paul |
—
|
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: Saint Paul | Statement: [Minnesota Mining and Manufacturing Company, headquartersLocationCity, Saint Paul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headquartersLocationCity Context triple: [Minnesota Mining and Manufacturing Company, headquartersLocationCity, Saint Paul]
-
A.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
B.
hasHeadOfficeCity
chosen
Indicates that an organization’s main or central administrative office is located in a particular city.
-
C.
sponsorHeadquartersCity
Indicates the city where the sponsoring organization’s main headquarters is located.
-
D.
provinceHeadquarters
Indicates that one entity serves as the main administrative or organizational headquarters for a province associated with the other entity.
-
E.
governingBodyHeadquartersCity
Indicates the city where the headquarters of a governing body is located.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d02d07b08190acbcbb646cd9a58e |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:11 p.m.