Triple

T7716003
Position Surface form Disambiguated ID Type / Status
Subject VASCO E174883 entity
Predicate callsign P1565 FINISHED
Object VASCO E174883 NE 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: VASCO | Statement: [VASCO, callsign, VASCO]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: VASCO
Context triple: [VASCO, callsign, VASCO]
  • A. VASCO chosen
    VASCO is a regional airline in Vietnam that operates domestic flights, often serving smaller airports and routes on behalf of Vietnam Airlines.
  • B. VASU
    VASU is the ICAO airport code for Surat Airport, a domestic airport serving the city of Surat in the Indian state of Gujarat.
  • C. VOSA
    VOSA was an executive agency of the UK government responsible for enforcing vehicle safety and environmental standards, and regulating operators of heavy goods and public service vehicles.
  • D. VUSAC
    VUSAC is the student government representing and advocating for students at Victoria University in the University of Toronto.
  • E. Vives Network
    Vives Network is a collaborative association of universities and higher education institutions in the Catalan-speaking regions that promotes academic, cultural, and research cooperation.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c6995c463c8190a14458036249d419 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c702cd0ddc8190aa23d998f55d0bd6 completed March 27, 2026, 10:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8b50cf3208190af9bb2d4126d381b completed March 29, 2026, 5:13 a.m.
Created at: March 27, 2026, 4:04 p.m.