Triple
T16411135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artemio Ricarte |
E398566
|
entity |
| Predicate | nickname |
P55
|
FINISHED |
| Object | Víbora |
E678409
|
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: Víbora | Statement: [Artemio Ricarte, nickname, Víbora]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Víbora Context triple: [Artemio Ricarte, nickname, Víbora]
-
A.
Víbora
chosen
Víbora is a traditional residential neighborhood in Havana, Cuba, known for its dense urban fabric and local commercial activity.
-
B.
Constrictor
Constrictor is a water slide attraction at Wet'n'Wild Gold Coast known for its tight twists and high-speed tube-style turns.
-
C.
Serpent
Serpent is a symmetric block cipher designed as a highly secure, conservative candidate for the Advanced Encryption Standard (AES) competition.
-
D.
Snake
Snake is a classic mobile arcade game in which the player guides a growing line to collect items while avoiding collisions with walls and its own tail.
-
E.
Snake
Snake is the codename of Solid Snake, the legendary special operations soldier and protagonist of the Metal Gear video game series.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328731a408190b38dcab0b7bb65ff |
completed | April 18, 2026, 6:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a003c66d41481909340f247f6e5393f |
completed | May 10, 2026, 8:05 a.m. |
Created at: April 10, 2026, 5:09 a.m.