Triple
T29595169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow trolleybus network |
E754272
|
entity |
| Predicate | notableDepot |
—
|
GENERATED |
| Object | Filevsky trolleybus depot |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDepot Context triple: [Moscow trolleybus network, notableDepot, Filevsky trolleybus depot]
-
A.
notableCargo
Indicates that an entity is known for carrying or having carried a particularly important, famous, or otherwise noteworthy cargo.
-
B.
notableDeployment
Indicates that an entity has been deployed or launched in a way that is particularly significant, prominent, or widely recognized.
-
C.
notableQuarry
Indicates that an entity is a quarry that is particularly significant, well-known, or noteworthy in some context.
-
D.
notableStore
Indicates that a store is recognized as notable or significant in some context (e.g., historically, culturally, or commercially).
-
E.
notableStoreType
Indicates that a store is particularly recognized or distinguished for being of a specified type (e.g., a notable example of that kind of store).
- F. None of above. chosen
Provenance (1 batch)
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. |
Created at: April 28, 2026, 6:17 p.m.