Triple
T893760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West 33rd Street |
E19296
|
entity |
| Predicate | commercialArea |
P20782
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [West 33rd Street, commercialArea, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialArea Context triple: [West 33rd Street, commercialArea, Yes]
-
A.
commercial
Indicates that one entity is engaged in a business-related or profit-oriented relationship, activity, or transaction with another entity.
-
B.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another entity.
-
C.
commercialArm
Indicates that an entity functions as the business or revenue-generating division/branch of another organization.
-
D.
commercialSignificance
Indicates that something has notable economic or business importance, value, or impact in a commercial context.
-
E.
commercialIntroduction
Indicates that one entity introduces or connects another entity to a commercial opportunity, partner, product, or service for business purposes.
- F. None of above. chosen
Provenance (4 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad212cd8819091eb1b7d606f5afd |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa9372e88190b5a9db4afdc045c6 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab4a38ec8190915916d80299ab55 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.