Triple
T15242525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Baltimore Sun |
E364292
|
entity |
| Predicate | printCirculationType |
P117722
|
FINISHED |
| Object | paid circulation |
—
|
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: paid circulation | Statement: [The Baltimore Sun, printCirculationType, paid circulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: printCirculationType Context triple: [The Baltimore Sun, printCirculationType, paid circulation]
-
A.
circulationType
Indicates the manner or category of movement, distribution, or flow associated with the related entities.
-
B.
hasCirculationFeature
Indicates that an entity possesses a specific feature related to movement or flow within a system, such as circulation paths, routes, or mechanisms.
-
C.
circulationFormat
Indicates the medium or format in which an item is made available for circulation or lending (e.g., physical, digital, audio).
-
D.
printType
Indicates the method or format by which something is printed or physically reproduced.
-
E.
hasPrimaryCirculation
Indicates that an entity possesses or is associated with a main or principal system, route, or pattern of circulation (such as movement, flow, or distribution).
- F. None of above. chosen
Provenance (4 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007dcc33081908545ea1a1d2c19fe |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:13 a.m.