Triple
T15270123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pasar Terapung Lok Baintan |
E364998
|
entity |
| Predicate | operatesFrequency |
P83979
|
FINISHED |
| Object | 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: daily | Statement: [Pasar Terapung Lok Baintan, operatesFrequency, daily]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesFrequency Context triple: [Pasar Terapung Lok Baintan, operatesFrequency, daily]
-
A.
operatingFrequencyApproximate
chosen
Indicates an approximate or estimated operating frequency at which an entity functions or is designed to function.
-
B.
hasBroadcastFrequency
Indicates that an entity operates or transmits at a specified broadcast frequency.
-
C.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
-
D.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
-
E.
usesElectricFrequency
Indicates that one entity operates or functions by relying on a specified electric frequency provided by another entity or context.
- 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.