Triple
T7002137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gotthard route |
E162360
|
entity |
| Predicate | passesThrough |
P225
|
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: [Gotthard route, passesThrough, Uri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Uri Context triple: [Gotthard route, passesThrough, 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.
"URY"
URY is the three-letter country code for Uruguay, used in international standards such as ISO 3166-1 alpha-3.
-
E.
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.
- 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc1115c48190a9363473ae21b6c1 |
completed | March 27, 2026, 7:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c76a310eb08190a0fc1de2814aea08 |
completed | March 28, 2026, 5:42 a.m. |
Created at: March 27, 2026, 2:33 p.m.