Triple
T19115423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portobello Road |
E467893
|
entity |
| Predicate | hasStreetMarketSince |
P2714
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Portobello Road, hasStreetMarketSince, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetMarketSince Context triple: [Portobello Road, hasStreetMarketSince, 19th century]
-
A.
hasMarketHall
Indicates that an entity possesses, contains, or is associated with a market hall as part of its facilities or structures.
-
B.
hasMarket
chosen
Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
-
C.
hasStreetFood
Indicates that one entity offers, features, or is associated with street food in relation to another entity.
-
D.
hasMarketTownHistory
Indicates that an entity has a historical association with functioning as a market town or possessing recognized market-town status in the past.
-
E.
hasHistoricStreet
Indicates that an entity is associated with or located on a street that has recognized historical significance.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e39736588190b80ddef77101641a |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.