Triple
T21401167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boost |
E527914
|
entity |
| Predicate | typicalUseFrequency |
P23478
|
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: [Boost, typicalUseFrequency, daily]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUseFrequency Context triple: [Boost, typicalUseFrequency, daily]
-
A.
usesFrequency
chosen
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
-
B.
typicalUseRatio
Indicates the proportion or share in which something is commonly or normally used relative to other possible uses or components.
-
C.
typicalUseDays
Indicates the usual or expected number of days over which something is used or intended to be used.
-
D.
serviceFrequencyType
Indicates how often a service occurs or is scheduled within a given time period.
-
E.
oftenUse
Indicates that one entity frequently or regularly uses, employs, or utilizes another entity.
- 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_69e0b520ee3c8190abddbee7e37e834c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b16f7c5081909475eb5bb6177955 |
completed | April 22, 2026, 11:30 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:15 p.m.