Triple
T36781421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korotia Bazar |
E908778
|
entity |
| Predicate | likelyMarketDays |
P12447
|
FINISHED |
| Object | multiple days per week |
—
|
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: multiple days per week | Statement: [Korotia Bazar, likelyMarketDays, multiple days per week]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyMarketDays Context triple: [Korotia Bazar, likelyMarketDays, multiple days per week]
-
A.
possibleLengthDays
Indicates that an entity can have a duration, measured in whole or fractional days, equal to the specified value.
-
B.
likelyActiveDuring
Indicates that an entity is expected or inferred to be active or functioning during a specified time period or context.
-
C.
hasDays
chosen
Indicates that an entity is associated with, spans, or occurs on specific days.
-
D.
isBusinessDayIn
Indicates that a given date falls on a recognized working day (non-weekend, non-holiday) within a specified calendar, region, or jurisdiction.
-
E.
hasMarket
Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
- 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_69f76e798aa08190ace31098d1b13e9f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:12 p.m.