Triple
T32512498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Toot’s Music Store |
E830973
|
entity |
| Predicate | hasNeighborBusiness |
P191961
|
FINISHED |
| Object | Moe’s Tavern |
—
|
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: Moe’s Tavern | Statement: [King Toot’s Music Store, hasNeighborBusiness, Moe’s Tavern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighborBusiness Context triple: [King Toot’s Music Store, hasNeighborBusiness, Moe’s Tavern]
-
A.
hasNearbyCommercialFacilities
chosen
Indicates that a place is located close to one or more commercial facilities, such as shops, restaurants, or other businesses.
-
B.
hasNearbyIndustry
Indicates that an entity is located close to one or more industrial facilities or activities.
-
C.
hasMajorCompanyNearby
Indicates that a location or entity is situated close to at least one large or significant company.
-
D.
hasBusinesses
Indicates that an entity owns, operates, or is associated with one or more businesses.
-
E.
hasOutletNear
Indicates that one entity has a physical outlet or branch located in close proximity to another specified location or 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
Created at: May 1, 2026, 1 a.m.