Triple
T34425643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rondo neighborhood |
E883659
|
entity |
| Predicate | majorDisruptionPeriod |
P112366
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [Rondo neighborhood, majorDisruptionPeriod, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorDisruptionPeriod Context triple: [Rondo neighborhood, majorDisruptionPeriod, 1950s]
-
A.
majorIncident
Indicates that an event qualifies as a serious, high-impact incident requiring urgent attention or response.
-
B.
causedTransportDisruption
Indicates that one entity was the cause of a disruption or interruption to the normal operation of a transport system or service.
-
C.
majorStop
Indicates that a location functions as a primary or significant stop along a route or service path, typically where vehicles regularly halt for boarding, alighting, or key operations.
-
D.
isMajorEventOf
chosen
Indicates that an event is a primary, significant, or defining occurrence within the context of another entity (such as a project, period, or process).
-
E.
collapsePeriod
Indicates the time span during which a structure, system, or entity undergoes or is subject to collapse.
- 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff49016dcc8190a8a43868c728b4f1 |
completed | May 9, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69ff4891924c8190b5be340e2520e012 |
completed | May 9, 2026, 2:45 p.m. |
Created at: May 1, 2026, 2 a.m.