Triple
T9903866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Packard's Corner |
E182353
|
entity |
| Predicate | typicalBusinesses |
P35312
|
FINISHED |
| Object | restaurants |
—
|
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: restaurants | Statement: [Packard's Corner, typicalBusinesses, restaurants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBusinesses Context triple: [Packard's Corner, typicalBusinesses, restaurants]
-
A.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another entity.
-
B.
notableBusinessType
chosen
Indicates that an entity is notably associated with, characterized by, or best known for a particular type of business.
-
C.
typicalEmployer
Indicates that one entity is the kind of organization or person that commonly or usually employs the other entity.
-
D.
eligibleBusinessType
Indicates that a business entity qualifies under specified criteria to be considered an eligible type for a particular program, rule, or context.
-
E.
centralBusiness
Indicates that an entity functions as the primary commercial or economic hub (central business area or role) in relation to another entity.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4e4f92c81908e38509416f19c78 |
completed | April 2, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69cd1d8c584081908b73de75eb18e438 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:40 p.m.