Triple
T5621509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Park Row newspaper district |
E147614
|
entity |
| Predicate | peakImportance |
P65467
|
FINISHED |
| Object | circa 1880s–1910s |
—
|
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: circa 1880s–1910s | Statement: [Park Row newspaper district, peakImportance, circa 1880s–1910s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakImportance Context triple: [Park Row newspaper district, peakImportance, circa 1880s–1910s]
-
A.
peakRating
Indicates the highest rating value that has been achieved or recorded for an entity over a given period or context.
-
B.
rankingImpact
Indicates how an entity’s position or level in a ranking is affected or influenced by another factor or action.
-
C.
politicalImportance
Indicates the degree to which something holds significance, influence, or priority within political processes, decisions, or power structures.
-
D.
importantSaint
Indicates that the subject is recognized as a particularly significant or highly revered saint within a religious or spiritual tradition.
-
E.
significantPort
Indicates that a port holds major importance in terms of trade, transportation, or strategic relevance within a given context.
- 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02211c8f4819090d19656c6eac2d4 |
completed | March 22, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f40df64819089a659ea00a835ef |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:40 p.m.