Triple

T21145818
Position Surface form Disambiguated ID Type / Status
Subject Fishnish E521050 entity
Predicate hasApproximateCrossingTime P22182 FINISHED
Object approximately 20 minutes 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: approximately 20 minutes | Statement: [Fishnish, hasApproximateCrossingTime, approximately 20 minutes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasApproximateCrossingTime
Context triple: [Fishnish, hasApproximateCrossingTime, approximately 20 minutes]
  • A. approximateCrossingTime chosen
    Indicates an estimated point in time when one entity is expected to cross or intersect another (such as a path, boundary, or trajectory).
  • B. hasNearbyCrossingPoint
    Indicates that one location has a crossing point (such as a bridge, crosswalk, or intersection) situated close to it.
  • C. hasAtGradeCrossingNearby
    Indicates that one entity (typically a location or segment) has a nearby at-grade crossing where two transportation paths intersect at the same level.
  • D. hasCrossingPoint
    Indicates that two or more entities intersect or share at least one common point in space or along their paths.
  • E. hadCrossingPoints
    Indicates that two entities intersected or overlapped at one or more specific points in space or time.
  • 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_69e0b50c6a848190a4e525a77a319b8a completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e723fcdb7c8190ae04d6ad9dff3187 completed April 21, 2026, 7:15 a.m.
PD Predicate disambiguation batch_69e5f5f8a5bc819081918c7fa8e4496d completed April 20, 2026, 9:46 a.m.
Created at: April 16, 2026, 2:58 p.m.