Triple
T4290453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Everest |
E97375
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Everest |
E270321
|
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: Everest | Statement: [George Everest, familyName, Everest]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Everest Context triple: [George Everest, familyName, Everest]
-
A.
Everest
chosen
Everest is the codename for the high-performance CPU cores used in Apple’s A16 Bionic chip.
-
B.
Mount Everest
Mount Everest is the world's highest mountain above sea level, located in the Himalayas on the border between Nepal and the Tibet Autonomous Region of China.
-
C.
Cho Oyu
Cho Oyu is the world’s sixth-highest mountain, an 8,188-meter peak in the Mahalangur Himal section of the Himalayas near the Nepal–China border.
-
D.
Kangchenjunga
Kangchenjunga is the world’s third-highest mountain, a massive peak in the eastern Himalayas on the border between Nepal and India.
-
E.
George Everest
George Everest was a 19th-century British surveyor and geographer who served as Surveyor General of India and lent his name to Mount Everest.
- 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_69b3454595848190a0e6bbb6a2bea040 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3507efb28819091a9d5b9161a5008 |
completed | March 12, 2026, 11:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5d06ccbf081908bc23b5f194b9587 |
completed | March 14, 2026, 9:17 p.m. |
Created at: March 12, 2026, 11:08 p.m.