Triple
T9889860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guanzhong region |
E181424
|
entity |
| Predicate | hasPass |
P11208
|
FINISHED |
| Object | Hangu Pass |
E827539
|
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: Hangu Pass | Statement: [Guanzhong region, hasPass, Hangu Pass]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hangu Pass Context triple: [Guanzhong region, hasPass, Hangu Pass]
-
A.
Hangu Pass
chosen
Hangu Pass is an ancient strategic mountain pass in China that historically served as a key gateway between the Central Plains and the western Guanzhong region.
-
B.
Huta Pass
Huta Pass is a mountain pass located in the Beskid Sądecki range of the Western Carpathians in southern Poland.
-
C.
Ganwoljae Pass
Ganwoljae Pass is a scenic mountain pass in Ulju-gun, South Korea, known for its panoramic views and popular hiking trails.
-
D.
Hochtor Pass
Hochtor Pass is a high mountain pass in the Austrian Alps, best known as a key point along the scenic Grossglockner High Alpine Road.
-
E.
Hanpo Pass
Hanpo Pass is a scenic mountain pass on Lushan Mountain in China, known for its dramatic cliffs, cloud seas, and panoramic views over the surrounding landscape.
- 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_69ca8283a6708190801af7a25a7ebb9f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb47dfa908190884e96e5e5d6f41f |
completed | April 2, 2026, 12:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d22891cb4c8190b4d378749599bdda |
completed | April 5, 2026, 9:17 a.m. |
Created at: March 30, 2026, 8:39 p.m.