Triple
T11204197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAP Express |
E265117
|
entity |
| Predicate | ICAOCode |
P419
|
FINISHED |
| Object | TAP |
E265113
|
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: TAP | Statement: [TAP Express, ICAOCode, TAP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TAP Context triple: [TAP Express, ICAOCode, TAP]
-
A.
TAP
chosen
TAP is the ICAO airline designator for TAP Air Portugal, the flag carrier airline of Portugal.
-
B.
TAP
TAP is a reusable smart fare card system used for paying transit fares across multiple public transportation agencies in the Los Angeles County area.
-
C.
TAPV
The TAPV (Tactical Armoured Patrol Vehicle) is a Canadian 4x4 armoured military vehicle designed for reconnaissance, patrol, and security missions with high protection against mines and improvised explosive devices.
-
D.
TAPS
TAPS is a major U.S. crude oil pipeline system that transports oil across Alaska from the North Slope to the ice-free port of Valdez.
-
E.
TAS
TAS is the commonly used French acronym for the Court of Arbitration for Sport, an international body that settles sports-related disputes through arbitration.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d355c481908fc3d555b596314d |
completed | April 9, 2026, 5:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4972bfbd481908cd0da59389ae17c |
completed | April 19, 2026, 8:49 a.m. |
Created at: April 8, 2026, 9:30 p.m.