Triple

T34577950
Position Surface form Disambiguated ID Type / Status
Subject Brooklyn Heights cantilever section E887809 entity
Predicate lowerDecksUsedFor P68896 FINISHED
Object vehicular traffic 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: vehicular traffic | Statement: [Brooklyn Heights cantilever section, lowerDecksUsedFor, vehicular traffic]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lowerDecksUsedFor
Context triple: [Brooklyn Heights cantilever section, lowerDecksUsedFor, vehicular traffic]
  • A. hasLowerDeckFunction chosen
    Indicates that an entity serves a specific role or performs a designated function on the lower deck of a structure or vehicle.
  • B. usedOnStarships
    Indicates that something is employed or applied in the context of starships, such as equipment, technology, or materials used aboard or for operating them.
  • C. upperDeckUsedFor
    Indicates that the upper deck of an object or structure is utilized for a specified purpose or activity.
  • D. eraUsedIn
    Indicates that something (such as a method, standard, or practice) was in active use during a specified historical or temporal era.
  • E. lowerDeckCargoPositions
    Indicates the specific locations or slots designated for storing cargo in the lower deck area.
  • 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_69f349d25cbc8190869998de5915886b completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7209b45e48190b08a5085d90865e5 completed May 3, 2026, 10:16 a.m.
PD Predicate disambiguation batch_69f71cc8074c81909ae09bea2acf1a09 completed May 3, 2026, 10 a.m.
Created at: May 1, 2026, 2:03 a.m.