Triple
T30082596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnston Press |
E764510
|
entity |
| Predicate | numberOfTitlesAtPeak |
P201990
|
FINISHED |
| Object | over 200 |
—
|
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: over 200 | Statement: [Johnston Press, numberOfTitlesAtPeak, over 200]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfTitlesAtPeak Context triple: [Johnston Press, numberOfTitlesAtPeak, over 200]
-
A.
peakedWithinTopTenOn
Indicates that something (such as a work, product, or performance) reached a highest ranking position within the top ten on a specified chart, list, or ranking system.
-
B.
numberOfWeeksAtNumberOne
Indicates the duration, measured in weeks, that something remained in the number-one position.
-
C.
numberOfTop10SinglesUS
Indicates the number of singles by an entity that have reached the top 10 positions on music charts in the United States.
-
D.
reachedPeakInDecade
Indicates that an entity attained its highest level, value, or prominence during a specified decade.
-
E.
numberOfTitlesHeldByRecordHolders
Indicates the total count of titles held by the entities that are recognized as record holders.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0041860fd081908623ef9fd40a9775 |
completed | May 10, 2026, 8:27 a.m. |
| PD | Predicate disambiguation | batch_6a00414b01488190a312adb3b25d69cf |
completed | May 10, 2026, 8:26 a.m. |
| PDg | Predicate description generation | batch_6a00418517008190b33399a08a003ee2 |
completed | May 10, 2026, 8:27 a.m. |
Created at: April 29, 2026, 7:03 p.m.