Triple

T30029417
Position Surface form Disambiguated ID Type / Status
Subject Exposition Corridor E762970 entity
Predicate alignmentRoughlyParallelTo P158086 FINISHED
Object Exposition Boulevard 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: Exposition Boulevard | Statement: [Exposition Corridor, alignmentRoughlyParallelTo, Exposition Boulevard]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: alignmentRoughlyParallelTo
Context triple: [Exposition Corridor, alignmentRoughlyParallelTo, Exposition Boulevard]
  • A. orientedParallelTo
    Indicates that one entity is parallel to another with a specified or consistent direction or orientation.
  • B. rotationAlignedWith
    Indicates that the orientation or rotational state of one entity is aligned or matched with that of another entity.
  • C. alignsWith
    Indicates that one entity is in agreement, harmony, or consistent correspondence with another in terms of position, direction, standard, or principle.
  • D. isPartiallyParallelTo chosen
    Indicates that two entities are aligned in roughly the same direction but not exactly parallel, sharing only a partial or approximate parallel relationship.
  • E. sometimesAlignedAs
    Indicates that two entities are occasionally in agreement, coordination, or matching orientation, but not consistently or permanently.
  • 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_69f2246ee6e48190b69e837b913b398a completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f679ae15908190b97e7356d8f62949 completed May 2, 2026, 10:24 p.m.
PD Predicate disambiguation batch_69f66ec9919881908a187bfc7c4df192 completed May 2, 2026, 9:38 p.m.
Created at: April 29, 2026, 6:49 p.m.