Triple

T7622099
Position Surface form Disambiguated ID Type / Status
Subject Cape Liberty Cruise Port E172520 entity
Predicate hasAccessTransportMode P37966 FINISHED
Object car 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: car | Statement: [Cape Liberty Cruise Port, hasAccessTransportMode, car]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAccessTransportMode
Context triple: [Cape Liberty Cruise Port, hasAccessTransportMode, car]
  • A. transportModeAccess chosen
    Indicates that one entity has the ability or permission to use, reach, or be served by a particular mode of transportation.
  • B. hasTransitAccessTo
    Indicates that one place or entity is reachable from another via public or shared transportation services.
  • C. hasPrimaryTransportationMode
    Indicates the main or most frequently used mode of transportation associated with an entity.
  • D. hasPublicTransitMode
    Indicates that a location, route, or service is associated with or supports a specific mode of public transportation (e.g., bus, train, tram).
  • E. hasTransportationRelation
    Indicates a relationship in which one entity provides, uses, is connected by, or is otherwise associated with a means or mode of transportation to another entity or location.
  • 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_69c699506b308190826894dab1d9ea86 completed March 27, 2026, 2:50 p.m.
NER Named-entity recognition batch_69c6fe73ff7c8190ab1218d97b37416d completed March 27, 2026, 10:02 p.m.
PD Predicate disambiguation batch_69c6f4e725a88190b1f05dd224f7f4f2 completed March 27, 2026, 9:21 p.m.
Created at: March 27, 2026, 3:56 p.m.