Triple
T6023039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Furka Pass |
E134108
|
entity |
| Predicate | connects |
P390
|
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: [Furka Pass, connects, Uri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Uri Context triple: [Furka Pass, connects, 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.
Ur
Ur was one of the most important ancient Sumerian city-states, renowned for its ziggurat and early urban civilization in southern Mesopotamia.
-
C.
RFC 3986
RFC 3986 is the Internet standard that defines the syntax and semantics of Uniform Resource Identifiers (URIs), superseding earlier URI specifications.
-
D.
URL Standard
The URL Standard is a technical specification by the WHATWG that defines how URLs are parsed, processed, and handled consistently across web browsers and platforms.
-
E.
URU
URU is the FIFA country code used to represent the Uruguay national football team in international competitions and rankings.
- 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_69c008742a5c8190b9cb9c2787a3d8b3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04fbd7978819085d683578bc62aa3 |
completed | March 22, 2026, 8:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c11371ceb88190b0c2d4218ed0327a |
completed | March 23, 2026, 10:18 a.m. |
Created at: March 22, 2026, 4:07 p.m.