Triple
T5194511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notting Hill |
E117235
|
entity |
| Predicate | marketSpeciality |
P43327
|
FINISHED |
| Object | antiques |
—
|
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: antiques | Statement: [Notting Hill, marketSpeciality, antiques]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketSpeciality Context triple: [Notting Hill, marketSpeciality, antiques]
-
A.
marketSpecialization
chosen
Indicates a relationship where an entity focuses its activities, products, or services on serving a specific segment or niche of a broader market.
-
B.
marketsIn
Indicates that one entity promotes, sells, or offers another entity’s products or services within a particular market or geographic area.
-
C.
marketType
Indicates the classification or category of market in which an entity operates or a transaction occurs (e.g., retail, wholesale, online).
-
D.
coreMarket
Indicates that an entity serves as the primary or most important market for another entity’s products, services, or activities.
-
E.
uniformSpecialty
Indicates that multiple entities share the same specific specialty, expertise, or area of focus.
- 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_69bd4462ed04819084fcb01eb9d2fa74 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adb034c819086bf8a85fbf158f4 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77b9a67c8190819612257ea746b4 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.