Triple
T13212713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 81 |
E314533
|
entity |
| Predicate | city |
P40
|
FINISHED |
| Object | Las Vegas |
E36474
|
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: Las Vegas | Statement: [UFC 81, city, Las Vegas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Las Vegas Context triple: [UFC 81, city, Las Vegas]
-
A.
Bas Vegas
Bas Vegas is a tongue-in-cheek nickname for the Essex town of Basildon, referencing its lively nightlife and entertainment venues in comparison to Las Vegas.
-
B.
Las Vegas, Nevada
chosen
Las Vegas, Nevada is a major resort city in the Mojave Desert known for its vibrant nightlife, casinos, entertainment, and luxury hotels.
-
C.
Reno
Reno is a small city located in Parker County in the U.S. state of Texas.
-
D.
Reno
Reno is a city in northwestern Nevada known for its casinos, tourism, and proximity to outdoor recreation areas in the Sierra Nevada, including Lake Tahoe.
-
E.
Santiago de las Vegas
Santiago de las Vegas is a town in the municipality of Boyeros, Havana, Cuba, historically known as a suburban settlement of the capital.
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c9f0f148190a0698ef27573c885 |
completed | April 10, 2026, 11:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f73973248481909ed29ea68955f447 |
completed | May 3, 2026, 12:02 p.m. |
Created at: April 9, 2026, 9:17 p.m.