Triple
T30888040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polly Sherman |
E786819
|
entity |
| Predicate | frequentlyCoversUpFor |
P25172
|
FINISHED |
| Object | Basil Fawlty |
—
|
NE NERFINISHED |
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: Basil Fawlty | Statement: [Polly Sherman, frequentlyCoversUpFor, Basil Fawlty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequentlyCoversUpFor Context triple: [Polly Sherman, frequentlyCoversUpFor, Basil Fawlty]
-
A.
isFrequentlyCovered
Indicates that an entity is regularly or commonly reported on, discussed, or featured, especially in media or informational sources.
-
B.
coverUpBy
chosen
Indicates that one entity conceals, suppresses, or hides the actions, information, or wrongdoing associated with another entity.
-
C.
isFrequentlyCoveredBy
Indicates that one entity is regularly or repeatedly reported on, discussed, or featured by another entity, such as a media outlet or information source.
-
D.
typicallyCovers
Indicates that one entity is the kind of thing that usually or normally includes, addresses, or encompasses another entity.
-
E.
isFrequentlyCoveredSince
Indicates that one entity has been regularly or repeatedly covered (e.g., in media, reports, or discussions) starting from a specified point in 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 8:49 p.m.