Triple

T21546209
Position Surface form Disambiguated ID Type / Status
Subject MD 32 E531628 entity
Predicate servesAsConnectorBetween P10516 FINISHED
Object suburban communities and major highways 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: suburban communities and major highways | Statement: [MD 32, servesAsConnectorBetween, suburban communities and major highways]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servesAsConnectorBetween
Context triple: [MD 32, servesAsConnectorBetween, suburban communities and major highways]
  • A. connectsTo
    Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
  • B. connectsPartOf
    Indicates a relationship where one entity serves to link or join a component to the larger whole of which that component is a part.
  • C. servesAsGatewayTo chosen
    Indicates that one entity functions as an entry point, access route, or intermediary channel that enables reaching or connecting to another entity.
  • D. connectsViaCanal
    Indicates that one entity is linked or joined to another by means of a canal.
  • E. hasConnector
    Indicates that one entity is linked or joined to another entity through a connector or connecting element.
  • 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_69e0c45f17148190949c330ab9c27706 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eeb58ef2548190a81ff51baba76e48 completed April 27, 2026, 1:02 a.m.
PD Predicate disambiguation batch_69e6320766308190ba5dca2f7c826aa4 completed April 20, 2026, 2:02 p.m.
Created at: April 16, 2026, 6:28 p.m.