Triple
T22065850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennsylvania Railroad tracks |
E545265
|
entity |
| Predicate | peakExpansionPeriod |
P6451
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Pennsylvania Railroad tracks, peakExpansionPeriod, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakExpansionPeriod Context triple: [Pennsylvania Railroad tracks, peakExpansionPeriod, late 19th century]
-
A.
peakRepressionPeriod
Indicates the time span during which acts of repression are at their highest intensity or frequency.
-
B.
peakServicePeriod
Indicates the time interval during which a service experiences its highest or most intensive level of use or operation.
-
C.
peakExportPeriod
Indicates the time period during which exports of a given item or from a given source reach their highest level.
-
D.
peakMiningPeriod
Indicates the time period during which mining activity for a given resource or location was at its highest level.
-
E.
timePeriodOfMajorExpansion
chosen
Indicates the time span during which the referenced entity underwent its most significant growth or expansion.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12883d2108190a6127783f8f635fc |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:27 p.m.