Triple
T21912323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sukawati art market |
E541094
|
entity |
| Predicate | hasTypicalClosingTime |
P33870
|
FINISHED |
| Object | late afternoon |
—
|
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: late afternoon | Statement: [Sukawati art market, hasTypicalClosingTime, late afternoon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalClosingTime Context triple: [Sukawati art market, hasTypicalClosingTime, late afternoon]
-
A.
closingTime
chosen
Indicates the specific time at which a place, service, or activity stops operating or becomes unavailable.
-
B.
typicalClosing
Indicates that an entity represents a standard or commonly used way of ending or concluding another entity (such as a message, document, or interaction).
-
C.
closureTime
Indicates the time at which an entity, event, or process is formally closed, ended, or no longer available.
-
D.
closingLocation
Indicates the place or venue where an event, process, or activity comes to an end or is formally concluded.
-
E.
isCloseted
Indicates that an individual conceals a particular aspect of their identity, such as sexual orientation or gender identity, from others.
- 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f121db1dc48190af5dc634431d863a |
completed | April 28, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:41 p.m.