Triple

T24989810
Position Surface form Disambiguated ID Type / Status
Subject T-10 E625414 entity
Predicate adjacentCodeDirectionEast P721 FINISHED
Object T-09 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: T-09 | Statement: [T-10, adjacentCodeDirectionEast, T-09]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: adjacentCodeDirectionEast
Context triple: [T-10, adjacentCodeDirectionEast, T-09]
  • A. directionEastSide
    Indicates that one entity is located on or oriented toward the eastern side of another entity.
  • B. adjacentStationTowardsSouth
    Indicates that one station is directly next to another in the southward direction along a route or line.
  • C. adjacentTimeZoneEast chosen
    Indicates that one time zone is directly to the east of another, sharing a common boundary without any intervening time zones.
  • D. adjacentCityNorth
    Indicates that one city is directly to the north of another city and shares a common boundary or is immediately neighboring it in that direction.
  • E. adjacentRouteWest
    Indicates that one route is directly adjacent to another on its western side.
  • 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_69e2ff2611c081908710457fbe6d376b completed April 18, 2026, 3:48 a.m.
NER Named-entity recognition batch_69f55e519978819087a1676564a74630 completed May 2, 2026, 2:15 a.m.
PD Predicate disambiguation batch_69f4a0edd10c81908a052ab864d57c54 completed May 1, 2026, 12:47 p.m.
Created at: April 18, 2026, 6:03 a.m.