Triple
T8812321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kennebec Journal |
E209695
|
entity |
| Predicate | hasEditionFrequency |
P1389
|
FINISHED |
| Object | 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: daily | Statement: [Kennebec Journal, hasEditionFrequency, daily]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEditionFrequency Context triple: [Kennebec Journal, hasEditionFrequency, daily]
-
A.
appliedToEditionFrequency
Indicates that a particular action, rule, or condition is associated with how often a specific edition occurs or is issued.
-
B.
publicationFrequency
chosen
Indicates how often a publication or content is issued, released, or made available over a given period.
-
C.
hasEditionIn
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
-
D.
numberOfEditions
Indicates the total count of distinct editions associated with a given entity.
-
E.
hasEditionType
Indicates that one entity is a specific edition type or format classification of another entity (such as a work, publication, or product).
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5feed07881909bbe116ae359346a |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.