Triple
T2223723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West 32nd Street |
E48598
|
entity |
| Predicate | hasCommercialUse |
P23616
|
FINISHED |
| Object | retail |
—
|
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: retail | Statement: [West 32nd Street, hasCommercialUse, retail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommercialUse Context triple: [West 32nd Street, hasCommercialUse, retail]
-
A.
hasCommercialFunction
chosen
Indicates that an entity serves a commercial role or purpose, such as engaging in trade, sales, or other profit-oriented activities.
-
B.
isNonCommercial
Indicates that the associated entity, use, or activity is not intended for or involved in commercial, profit-generating purposes.
-
C.
hasOfficialUse
Indicates that something is used in an authorized or formally recognized capacity, typically by an official body or for official purposes.
-
D.
isUsedUnder
Indicates that one entity is utilized or applied within the context, conditions, or framework defined by another entity.
-
E.
isCommercialPublication
Indicates that the referenced work is a publication produced or distributed for commercial purposes, typically involving sale or profit.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc03d1df88190950c691a4c246bd1 |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdac31d8819092d17815e11921e9 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.