Triple
T11907854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tumble Monkeys acrobatic troupe |
E283315
|
entity |
| Predicate | hasPerformanceFrequency |
P16914
|
FINISHED |
| Object | multiple times 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: multiple times daily | Statement: [Tumble Monkeys acrobatic troupe, hasPerformanceFrequency, multiple times daily]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformanceFrequency Context triple: [Tumble Monkeys acrobatic troupe, hasPerformanceFrequency, multiple times daily]
-
A.
performedFrequency
chosen
Indicates how often an action or activity is carried out within a given time period.
-
B.
operatingFrequencyApproximate
Indicates an approximate or estimated operating frequency at which an entity functions or is designed to function.
-
C.
hasClockSpeed
Indicates that an entity (typically a processor or device) operates at a specified clock frequency or speed.
-
D.
hasFrequencyCategory
Indicates that something is associated with a particular classification of how often it occurs or is used.
-
E.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e5264b2081909bda6c24abb89725 |
completed | April 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.