Triple
T953474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubai Fountain |
E20573
|
entity |
| Predicate | showFrequency |
P85
|
FINISHED |
| Object | evenings and selected daytime shows |
—
|
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: evenings and selected daytime shows | Statement: [Dubai Fountain, showFrequency, evenings and selected daytime shows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showFrequency Context triple: [Dubai Fountain, showFrequency, evenings and selected daytime shows]
-
A.
performedFrequency
Indicates how often an action or activity is carried out within a given time period.
-
B.
frequencyComparedTo
Indicates how often one event or action occurs relative to another, expressing a comparison of their frequencies.
-
C.
hasFrequencyNote
Indicates that something is associated with a specific note describing how often it occurs or is repeated.
-
D.
frequency
chosen
Indicates how often an event, action, or relationship occurs within a given period or context.
-
E.
selectionRankingFrequency
Indicates how often an entity is chosen or ranked in a particular position within a selection or ordering process.
- 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3d8f2e0819097554a301f8aa70f |
completed | March 1, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a045308190ab94f3adab40db8d |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.