Triple
T16695337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blink-182 |
E405701
|
entity |
| Predicate | hasShortName |
P1354
|
FINISHED |
| Object | Blink |
E405701
|
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: Blink | Statement: [Blink-182, hasShortName, Blink]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Blink Context triple: [Blink-182, hasShortName, Blink]
-
A.
Blink
Blink is an open-source web browser engine developed primarily by Google and used in several major browsers to render web pages.
-
B.
Blink
Blink is a bestselling nonfiction book by Malcolm Gladwell that explores the power and pitfalls of rapid, intuitive decision-making.
-
C.
Blink
chosen
Blink is the abbreviated name commonly used for Blink-182, the American rock band known for its catchy pop-punk songs and irreverent humor.
-
D.
Blink
"Blink" is a widely acclaimed, time-bending episode of the British science fiction series Doctor Who, renowned for introducing the terrifying Weeping Angels and its minimal use of the Doctor.
-
E.
Blink
Blink is Tracer’s signature short-range teleportation move in Overwatch, allowing her to rapidly reposition in quick bursts.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37eacfa788190a8d2058f96c0d445 |
completed | April 18, 2026, 12:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00919acd308190a3f29040554b9cfc |
completed | May 10, 2026, 2:09 p.m. |
Created at: April 10, 2026, 5:19 a.m.