Triple

T6615514
Position Surface form Disambiguated ID Type / Status
Subject Brouwer Route E149339 entity
Predicate timeSavedComparedToOlderRoutes P71530 FINISHED
Object several weeks per voyage 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: several weeks per voyage | Statement: [Brouwer Route, timeSavedComparedToOlderRoutes, several weeks per voyage]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timeSavedComparedToOlderRoutes
Context triple: [Brouwer Route, timeSavedComparedToOlderRoutes, several weeks per voyage]
  • A. previousTravelTimeOnRoute
    Indicates the duration of travel that occurred earlier on the same route before the current segment or time period.
  • B. significantlyShortensRouteBetween
    Indicates that one entity provides a connection between two others that makes the path or travel distance between them substantially shorter than alternative routes.
  • C. travelTimeCategory
    Indicates the qualitative classification of how long a given travel or trip duration is (e.g., short, medium, long).
  • D. totalRouteLength
    Indicates the overall distance or length of an entire route when all its segments are combined.
  • E. popularityRelativeToOtherRoutes
    Indicates how popular a given route is compared to other available routes.
  • 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_69c687ebc680819094caf71faba2efe2 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6bdb88cc881908f35648c15a7dc85 completed March 27, 2026, 5:26 p.m.
PD Predicate disambiguation batch_69c6ad007c1c8190af425f51011c7ad1 completed March 27, 2026, 4:14 p.m.
PDg Predicate description generation batch_69c6bdb76ec48190b59d576170970cc9 completed March 27, 2026, 5:26 p.m.
Created at: March 27, 2026, 1:57 p.m.