Triple
T4595290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewelry District |
E100187
|
entity |
| Predicate | hasStreetActivity |
P19746
|
FINISHED |
| Object | showrooms |
—
|
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: showrooms | Statement: [Jewelry District, hasStreetActivity, showrooms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetActivity Context triple: [Jewelry District, hasStreetActivity, showrooms]
-
A.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
-
B.
hasStreetLevel
Indicates that something is located at, accessible from, or directly associated with the street level of a building or area.
-
C.
pedestrianActivity
Indicates that an entity is engaged in or associated with walking or other on-foot movement or behavior.
-
D.
hasActivityIn
chosen
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
E.
hasNotableStreet
Indicates that an entity is associated with a particular street that is considered notable or significant.
- 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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd593f25888190a4f219e4da494764 |
completed | March 20, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:11 p.m.