Triple
T19769543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Station Road market |
E474846
|
entity |
| Predicate | likelyOpeningPattern |
P27375
|
FINISHED |
| Object | open daily |
—
|
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: open daily | Statement: [Station Road market, likelyOpeningPattern, open daily]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyOpeningPattern Context triple: [Station Road market, likelyOpeningPattern, open daily]
-
A.
typicalOpeningPattern
chosen
Indicates that there is a commonly occurring or characteristic initial configuration, sequence, or arrangement associated with the given context.
-
B.
likelyBehavior
Indicates the behavior or action that an entity is expected or predicted to exhibit under given circumstances.
-
C.
reopeningPattern
Indicates a recurring or structured way in which something that was previously closed or inactive is opened or resumed again over time.
-
D.
likelyComposition
Indicates that one entity is probably a component or constituent part of another entity, though this compositional relationship is uncertain or inferred rather than definite.
-
E.
likelySource
Indicates that one entity is considered the probable origin or cause of another entity or event.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6535ab298819085263dc37cc898cb |
completed | April 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.