Triple

T7996528
Position Surface form Disambiguated ID Type / Status
Subject Amsterdam bridge network E186139 entity
Predicate supportsModeOfTransport P43182 FINISHED
Object cars 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: cars | Statement: [Amsterdam bridge network, supportsModeOfTransport, cars]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsModeOfTransport
Context triple: [Amsterdam bridge network, supportsModeOfTransport, cars]
  • A. supportsMobilityType chosen
    Indicates that one entity provides compatibility with, or can function using, a specified type of mobility or movement mode.
  • B. appliesToTransportMode
    Indicates that a rule, condition, or characteristic is specifically associated with and relevant to a particular mode of transport.
  • C. hasFormOfPublicTransit
    Indicates that one entity provides or is associated with a particular type or mode of public transportation for another entity or context.
  • D. hasPrimaryTransportationMode
    Indicates the main or most frequently used mode of transportation associated with an entity.
  • E. hasPublicTransitMode
    Indicates that a location, route, or service is associated with or supports a specific mode of public transportation (e.g., bus, train, tram).
  • 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_69ca829c6c308190ab05b43d234c52b2 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3c97968481908d261b3f0bd6b8e6 completed March 31, 2026, 3:16 a.m.
PD Predicate disambiguation batch_69cb0483d3b48190b250c7603d747bca completed March 30, 2026, 11:17 p.m.
Created at: March 30, 2026, 5:17 p.m.