Triple

T5735438
Position Surface form Disambiguated ID Type / Status
Subject Flatbush Avenue–Brooklyn College E126489 entity
Predicate hasTerminalLayout P10827 FINISHED
Object stub-end terminal 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: stub-end terminal | Statement: [Flatbush Avenue–Brooklyn College, hasTerminalLayout, stub-end terminal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTerminalLayout
Context triple: [Flatbush Avenue–Brooklyn College, hasTerminalLayout, stub-end terminal]
  • A. hasLayout chosen
    Indicates that one entity defines or is associated with the structural arrangement or organization (layout) of another entity.
  • B. hasTerminalShape
    Indicates that one entity possesses or exhibits a particular terminal (end) shape defined by another entity.
  • C. hasIntegratedTerminal
    Indicates that one entity includes or supports a built-in terminal interface as part of its functionality.
  • D. hasSubTerminal
    Indicates that an entity includes or is associated with a subordinate or lower-level terminal element within a hierarchical structure.
  • E. hasTerminalFunction
    Indicates that something possesses a function or role specifically associated with an endpoint, boundary, or final stage within a system or process.
  • 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_69c0083082288190b7478cead6b5430a completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c025596b5c81909b5626773c91cecb completed March 22, 2026, 5:22 p.m.
PD Predicate disambiguation batch_69c021c8195481909419808b002628aa completed March 22, 2026, 5:07 p.m.
Created at: March 22, 2026, 3:47 p.m.