Triple
T2077684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TJVQ |
E44964
|
entity |
| Predicate | hasIATAcode |
P2569
|
FINISHED |
| Object | VQS |
E44963
|
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: VQS | Statement: [TJVQ, hasIATAcode, VQS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VQS Context triple: [TJVQ, hasIATAcode, VQS]
-
A.
VQS
chosen
VQS is the IATA airport code for Antonio Rivera Rodríguez Airport, which serves the island of Vieques in Puerto Rico.
-
B.
QQS
QQS is the IATA airport code for the Shuttle Landing Facility at NASA’s Kennedy Space Center in Florida, historically used for Space Shuttle landings.
-
C.
QQS
QQS is the IATA station code for London St Pancras International, a major central London railway terminus and international high-speed rail hub.
-
D.
CQF
CQF (Cyclic Queuing and Forwarding) is a time-sensitive networking mechanism defined in IEEE 802.1Qch that provides deterministic, low-latency packet forwarding using cyclic transmission queues.
-
E.
VVS
VVS was the air force branch of the Soviet Union’s armed forces, responsible for military aviation and air defense operations.
- 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_69a88916c2b48190a5ca2e9b12cad3ed |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba31eef8819081cf7f5334b59fe1 |
completed | March 7, 2026, 5:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae2734a0688190a43c9687af48d06d |
completed | March 9, 2026, 1:49 a.m. |
Created at: March 4, 2026, 7:41 p.m.