Triple
T34558932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dapitan Street |
E887284
|
entity |
| Predicate | hasTypicalEstablishment |
P83958
|
FINISHED |
| Object | eateries |
—
|
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: eateries | Statement: [Dapitan Street, hasTypicalEstablishment, eateries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalEstablishment Context triple: [Dapitan Street, hasTypicalEstablishment, eateries]
-
A.
hasEstablishment
chosen
Indicates that one entity possesses, operates, or is associated with a particular establishment (such as a business, facility, or institution).
-
B.
establishmentType
Indicates the specific kind or category of establishment that an entity is classified as.
-
C.
hasDrinkingEstablishmentType
Indicates the specific kind or category of drinking establishment associated with an entity (e.g., bar, pub, nightclub).
-
D.
operatedEstablishmentIn
Indicates that an entity ran or managed an establishment located within a specified place or jurisdiction.
-
E.
isCommercialFacility
Indicates that a facility is used primarily for commercial or business-related activities or services.
- 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_69f349d0c4d881908dd0950f5eb9ec0a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
Created at: May 1, 2026, 2:02 a.m.