Triple
T29595190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow trolleybus network |
E754272
|
entity |
| Predicate | heritageVehicle |
P180527
|
FINISHED |
| Object | preserved ZiU-9 trolleybuses |
—
|
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: preserved ZiU-9 trolleybuses | Statement: [Moscow trolleybus network, heritageVehicle, preserved ZiU-9 trolleybuses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageVehicle Context triple: [Moscow trolleybus network, heritageVehicle, preserved ZiU-9 trolleybuses]
-
A.
heritageVehicleType
Indicates the specific category or type of a vehicle that is considered part of cultural, historical, or heritage transport.
-
B.
historicRacingCar
Indicates that an entity is a racing car of historical significance, typically from a past era of motorsport competition.
-
C.
vehicleBase
Indicates that one entity serves as the foundational or underlying base for a vehicle-related entity or system.
-
D.
producedVehicle
Indicates that one entity manufactured or created a particular vehicle.
-
E.
vehicleDeveloped
Indicates that an entity (such as a person, organization, or group) created, designed, or otherwise developed a particular vehicle.
- 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: April 28, 2026, 6:17 p.m.