Triple

T5522003
Position Surface form Disambiguated ID Type / Status
Subject Temple Street (New Haven) E144830 entity
Predicate hasOrientationRelativeTo P42535 FINISHED
Object alongside New Haven Green 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: alongside New Haven Green | Statement: [Temple Street (New Haven), hasOrientationRelativeTo, alongside New Haven Green]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOrientationRelativeTo
Context triple: [Temple Street (New Haven), hasOrientationRelativeTo, alongside New Haven Green]
  • A. hasOrientation
    Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
  • B. hasRegionalOrientation
    Indicates that an entity is oriented toward, focused on, or primarily associated with a specific geographic region.
  • C. hasRelativeLocation
    Indicates that one entity is positioned in space in relation to another entity’s location.
  • D. hasFieldOrientation
    Indicates that one entity has a specified directional or spatial orientation relative to a field (such as magnetic, electric, or visual field).
  • E. positionedRelativeTo chosen
    Indicates that one entity’s spatial location is defined or described in relation to the position of another entity.
  • 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_69c008f873a481909b4d9f7e2db3c37d completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c01f7227a8819080c9f074afe0eaac completed March 22, 2026, 4:57 p.m.
PD Predicate disambiguation batch_69c01b0a06348190b39ac9fe80d2836a completed March 22, 2026, 4:38 p.m.
Created at: March 22, 2026, 3:33 p.m.