Triple
T34791642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Punch Office |
E1002963
|
entity |
| Predicate | publicationFrequencyOfMainTitle |
P1389
|
FINISHED |
| Object | weekly |
—
|
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: weekly | Statement: [Punch Office, publicationFrequencyOfMainTitle, weekly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationFrequencyOfMainTitle Context triple: [Punch Office, publicationFrequencyOfMainTitle, weekly]
-
A.
publicationFrequency
chosen
Indicates how often a publication or content is issued, released, or made available over a given period.
-
B.
publicationPeriod
Indicates the span of time during which something is published, active in publication, or valid as a published work.
-
C.
conferenceFrequency
Indicates how often a conference or similar recurring event takes place within a given time period.
-
D.
publicationPeriodDiscussed
Indicates that the time span or period during which a work was published is being discussed or analyzed in relation to something else.
-
E.
publishedIn
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff5803c02c81908b63067119f5e684 |
completed | May 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ff576d8b308190b49a1e072a0ae661 |
completed | May 9, 2026, 3:49 p.m. |
Created at: May 3, 2026, 3:59 p.m.