Triple
T13007627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parap Markets |
E322328
|
entity |
| Predicate | openingFrequency |
P17011
|
FINISHED |
| Object | weekly |
—
|
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: weekly | Statement: [Parap Markets, openingFrequency, weekly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingFrequency Context triple: [Parap Markets, openingFrequency, weekly]
-
A.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
-
B.
openingHoursCharacteristic
chosen
Indicates a relationship that specifies particular attributes or features of an entity’s opening hours, such as patterns, exceptions, or special conditions.
-
C.
openedBetween
Indicates that an entity was opened during a time interval that falls between two specified temporal bounds.
-
D.
openStatus
Indicates whether an entity (such as a place, service, or resource) is currently open or available for use.
-
E.
openingDay
Indicates the specific day on which something, typically an event, season, or venue, officially begins or first opens to the public.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e9cf0108190b02f498c6ccc91f8 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:48 p.m.