Triple
T3302913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petoskey stones |
E69375
|
entity |
| Predicate | commonUseLocation |
P21833
|
FINISHED |
| Object | gift shops in northern Michigan |
—
|
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: gift shops in northern Michigan | Statement: [Petoskey stones, commonUseLocation, gift shops in northern Michigan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonUseLocation Context triple: [Petoskey stones, commonUseLocation, gift shops in northern Michigan]
-
A.
typicalUseLocation
chosen
Indicates the usual or most common location where an entity is used or operates.
-
B.
agingLocation
Indicates the place where an entity undergoes an aging process or is stored to age over time.
-
C.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
D.
usedAsLocationIn
Indicates that something serves as the setting or place where another event, action, or situation occurs.
-
E.
mainLocation
Indicates that one entity serves as the primary or central location associated with 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0c662308190aad8b2a93e1c8a5c |
completed | March 8, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.