Triple
T8712731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westminster Quarters |
E206815
|
entity |
| Predicate | playsFrequency |
P23478
|
FINISHED |
| Object | every quarter hour on clocks that use it |
—
|
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: every quarter hour on clocks that use it | Statement: [Westminster Quarters, playsFrequency, every quarter hour on clocks that use it]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsFrequency Context triple: [Westminster Quarters, playsFrequency, every quarter hour on clocks that use it]
-
A.
performedFrequency
Indicates how often an action or activity is carried out within a given time period.
-
B.
gamesFrequency
Indicates how often the related entities engage in playing games together or participate in game-related activities.
-
C.
usesFrequency
chosen
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
-
D.
numberOfPlays
Indicates the total count of times an item, such as a track or media asset, has been played.
-
E.
frequencyComparedTo
Indicates how often one event or action occurs relative to another, expressing a comparison of their frequencies.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5c32aebc8190ba19299ce9a18efd |
completed | March 31, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.