Triple
T21411526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ripon Hornblower |
E528182
|
entity |
| Predicate | performsFrequency |
P16914
|
FINISHED |
| Object | every night |
—
|
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 night | Statement: [Ripon Hornblower, performsFrequency, every night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsFrequency Context triple: [Ripon Hornblower, performsFrequency, every night]
-
A.
performedFrequency
chosen
Indicates how often an action or activity is carried out within a given time period.
-
B.
frequentPerformance
Indicates that an entity regularly or repeatedly carries out a particular performance or activity over a period of time.
-
C.
isFrequentlyPerformedBy
Indicates that an action or activity is carried out often or on a regular basis by a particular entity.
-
D.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
-
E.
performsInNumber
Indicates that an entity takes part as a performer in a specific musical, theatrical, or similar numbered production or piece.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b1fe2cd08190bfaf28daae4f5233 |
completed | April 22, 2026, 11:33 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:43 p.m.