Triple
T5146162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portobello Road Market |
E116074
|
entity |
| Predicate | typicalClosingTimeSaturday |
P14959
|
FINISHED |
| Object | around 19:00 |
—
|
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: around 19:00 | Statement: [Portobello Road Market, typicalClosingTimeSaturday, around 19:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalClosingTimeSaturday Context triple: [Portobello Road Market, typicalClosingTimeSaturday, around 19:00]
-
A.
closingTime
Indicates the specific time at which a place, service, or activity stops operating or becomes unavailable.
-
B.
typicalEndHourLocal
chosen
Indicates the usual local-time clock hour at which an activity, event, or operation typically ends.
-
C.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
-
D.
openingHoursCharacteristic
Indicates a relationship that specifies particular attributes or features of an entity’s opening hours, such as patterns, exceptions, or special conditions.
-
E.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
- 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_69bd4446c0e08190a7c29dc74976bf03 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd78d7f4d081908d59adcd86f52f1d |
completed | March 20, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69bd77ae2f10819098bb8939106e1281 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:43 p.m.