Triple
T28151960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bulletin (magazine) |
E714641
|
entity |
| Predicate | laterEditionFrequency |
P1389
|
FINISHED |
| Object | fortnightly |
—
|
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: fortnightly | Statement: [The Bulletin (magazine), laterEditionFrequency, fortnightly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterEditionFrequency Context triple: [The Bulletin (magazine), laterEditionFrequency, fortnightly]
-
A.
laterFrequency
Indicates that one event, state, or action occurs with a lower frequency than another in a temporal sequence.
-
B.
appliedToEditionFrequency
Indicates that a particular action, rule, or condition is associated with how often a specific edition occurs or is issued.
-
C.
publicationFrequency
chosen
Indicates how often a publication or content is issued, released, or made available over a given period.
-
D.
hasEditionInterval
Indicates that there is a specific time interval during which an edition of something (e.g., a work, product, or version) is valid, applicable, or in effect.
-
E.
seriesFrequency
Indicates how often the events or items in a recurring series occur 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_69efd6b033208190bf74f80a147e2092 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: April 27, 2026, 10 p.m.