Triple
T3682531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stockholm tramways |
E78142
|
entity |
| Predicate | modernTramRevival |
P50292
|
FINISHED |
| Object | late 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: late 20th century | Statement: [Stockholm tramways, modernTramRevival, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernTramRevival Context triple: [Stockholm tramways, modernTramRevival, late 20th century]
-
A.
hasTramway
Indicates that a location or area is served by, contains, or is connected to a tramway system.
-
B.
formerRollingStock
Indicates that an entity was previously used as rolling stock (e.g., railway vehicles) but no longer serves in that capacity.
-
C.
futureRollingStock
Indicates that an entity is designated to serve as rolling stock (e.g., trains or rail vehicles) at some point in the future, rather than in the present or past.
-
D.
trains
Indicates that one entity teaches, instructs, or coaches another entity to develop skills, knowledge, or abilities.
-
E.
replacedRollingStock
Indicates that one rolling stock asset has been substituted or superseded by another in service or operational use.
- 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.