Triple
T3682528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stockholm tramways |
E78142
|
entity |
| Predicate | historicalTramEra |
P50290
|
FINISHED |
| Object | early 20th 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: early 20th century | Statement: [Stockholm tramways, historicalTramEra, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalTramEra Context triple: [Stockholm tramways, historicalTramEra, early 20th century]
-
A.
hasRailroadHistory
Indicates that an entity is associated with, involved in, or notable for historical events, operations, or developments related to railroads.
-
B.
hasRailroadHistoryWith
Indicates a historical relationship or connection between entities involving railroads, such as shared development, operation, or significant events in railway history.
-
C.
historicalTerminus
Indicates that one entity serves as the historically recognized endpoint or final limit of another entity, such as a route, period, or process.
-
D.
hasTramway
Indicates that a location or area is served by, contains, or is connected to a tramway system.
-
E.
openingDateOfTramTerminus
Indicates the date on which a tram terminus was officially opened for service.
- 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_69ad85e18c1c8190be8aafb227f39f48 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc4948cc48190ab1f59cc4a2437cc |
completed | March 8, 2026, 6:48 p.m. |
| PD | Predicate disambiguation | batch_69adb84be1fc81909721c871babb4633 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb97cdb788190a5ce96b21bd157ab |
completed | March 8, 2026, 6:01 p.m. |
Created at: March 8, 2026, 3:25 p.m.