Triple

T21610984
Position Surface form Disambiguated ID Type / Status
Subject Airport Way (Cambridge) E533305 entity
Predicate hasName P744 FINISHED
Object Airport Way 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: Airport Way | Statement: [Airport Way (Cambridge), hasName, Airport Way]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Airport Way
Context triple: [Airport Way (Cambridge), hasName, Airport Way]
  • A. Airport Way chosen
    Airport Way is a road in Cambridge, England, serving as a key access route to Cambridge City Airport and nearby transport links.
  • B. Airport Way
    Airport Way is a major roadway in Portland, Oregon that provides access to Portland International Airport and nearby commercial areas.
  • C. Airport Park
    Airport Park is a public recreational park in Colchester, Vermont, featuring open green spaces and outdoor facilities for community activities and sports.
  • D. Airport Spur
    Airport Spur is a segment of the Constitution Trail that branches off to provide a dedicated multi-use path connection toward the local airport area.
  • E. Aviation Avenue
    Aviation Avenue is a street whose name reflects an association with air travel or nearby aviation-related facilities.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c46411108190bba0d4176dffc9f3 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef17e88f7081909371bc0de2147609 completed April 27, 2026, 8:01 a.m.
Created at: April 16, 2026, 6:33 p.m.