Triple
T15270096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pasar Terapung Lok Baintan |
E364998
|
entity |
| Predicate | typicalTradingTime |
P2917
|
FINISHED |
| Object | dawn |
—
|
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: dawn | Statement: [Pasar Terapung Lok Baintan, typicalTradingTime, dawn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTradingTime Context triple: [Pasar Terapung Lok Baintan, typicalTradingTime, dawn]
-
A.
tradingHoursType
Indicates the classification of an entity’s trading hours, such as whether they are regular, extended, holiday-specific, or of another defined type.
-
B.
hasTradingHours
chosen
Indicates that an entity operates or is available for trading during specified time periods.
-
C.
tradingHoursTimezone
Indicates the time zone in which an entity’s trading hours are defined and observed.
-
D.
tradingSegment
Indicates that one entity operates within, or is associated with, a specific trading segment or market subdivision for transactional activities.
-
E.
hasTradingSession
Indicates that an entity participates in or is associated with a specific trading session or period during which trading activities occur.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0094eac848190a1740ae1aa6b28e0 |
completed | April 15, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.