Triple
T146479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zip2 |
E3340
|
entity |
| Predicate | businessFocus |
P71
|
FINISHED |
| Object | local business discovery |
—
|
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: local business discovery | Statement: [Zip2, businessFocus, local business discovery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: businessFocus Context triple: [Zip2, businessFocus, local business discovery]
-
A.
commercial
Indicates that one entity is engaged in a business-related or profit-oriented relationship, activity, or transaction with another entity.
-
B.
sector
chosen
Indicates that an entity operates in, belongs to, or is associated with a particular economic or industrial sector.
-
C.
market
Indicates the act of promoting, advertising, or selling a product, service, or idea to potential buyers or target audiences.
-
D.
economicAspect
Indicates that something is related to, characterized by, or has implications for economic factors, conditions, or outcomes.
-
E.
economicUse
Indicates that one entity utilizes another for economic purposes, such as production, trade, revenue generation, or cost-saving activities.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256580c2c8190beecca60ca8595f3 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.