Triple

T26271317
Position Surface form Disambiguated ID Type / Status
Subject Farragut Crossing (virtual tunnel) E660429 entity
Predicate transferZone P57570 FINISHED
Object downtown Washington, D.C. NE NERFINISHED

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: downtown Washington, D.C. | Statement: [Farragut Crossing (virtual tunnel), transferZone, downtown Washington, D.C.]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: transferZone
Context triple: [Farragut Crossing (virtual tunnel), transferZone, downtown Washington, D.C.]
  • A. transferBetween
    Indicates a movement or handover of something from one entity to another, typically changing its location, ownership, or control between them.
  • B. transferCorridor
    Indicates a relationship where something moves or is passed from one side or entity to another through an intermediate passage or channel.
  • C. transferDestination chosen
    Indicates the entity that serves as the receiving end or target location of a transfer from another entity.
  • D. transferWithinSystem
    Indicates the movement or reassignment of something from one part or component of a system to another part or component within the same overall system.
  • E. transferFeature
    Indicates a relationship where a feature, attribute, or capability is moved or reassigned from one entity to another.
  • 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_69ee812960d081909cff6085cc9fa3a6 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f707f7959881908f037f0d6b1d0c36 completed May 3, 2026, 8:31 a.m.
PD Predicate disambiguation batch_69f700fc274c8190a128593dc7c7abd0 completed May 3, 2026, 8:02 a.m.
Created at: April 26, 2026, 9:50 p.m.