Triple
T8502821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uri Geller |
E201263
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Uri |
E256636
|
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: Uri | Statement: [Uri Geller, givenName, Uri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Uri Context triple: [Uri Geller, givenName, Uri]
-
A.
Uri
chosen
Uri is a historic Swiss canton in central Switzerland, known as one of the founding members of the Swiss Confederation.
-
B.
Uris
Uris is a surname most notably associated with American novelist Leon Uris, known for his historical fiction works such as "Exodus."
-
C.
Urlați
Urlați is a small town in Romania known for its vineyards and wine production, located in Prahova County in the historical region of Muntenia.
-
D.
Urla
Urla is a coastal town and district on Turkey’s Aegean coast known for its vineyards, olive groves, and relaxed seaside atmosphere near the city of İzmir.
-
E.
UR
UR is the vehicle registration code used on license plates for vehicles registered in the Swiss canton of Uri.
- 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_69ca831fe47c8190b5c57b456d2aefa0 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe59c413881909513d8a9d52333c0 |
completed | March 31, 2026, 3:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce4e1da7388190855ccd2e4292fd26 |
completed | April 2, 2026, 11:08 a.m. |
Created at: March 30, 2026, 6:14 p.m.