Triple
T19040990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trans-Alaska Pipeline System |
E465999
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | TAPS |
—
|
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: TAPS | Statement: [Trans-Alaska Pipeline System, alsoKnownAs, TAPS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TAPS Context triple: [Trans-Alaska Pipeline System, alsoKnownAs, TAPS]
-
A.
TAPS
chosen
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.
-
B.
Tapper
Tapper is a surname most notably associated with English actress Zoe Tapper.
-
C.
TAP
TAP is a scholarly journal published by the Association for Computing Machinery that focuses on research in applied perception and related areas of computer science.
-
D.
TAP
TAP is the ICAO airline designator for TAP Air Portugal, the flag carrier airline of Portugal.
-
E.
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.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d80054c88190a9d3a49aed504235 |
completed | April 20, 2026, 7:38 a.m. |
Created at: April 10, 2026, 12:02 p.m.