Triple
T27312500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandakphu |
E689245
|
entity |
| Predicate | viewNickname |
P162183
|
FINISHED |
| Object | Sleeping Buddha view of Kanchenjunga range |
—
|
NE NERFINISHED |
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: Sleeping Buddha view of Kanchenjunga range | Statement: [Sandakphu, viewNickname, Sleeping Buddha view of Kanchenjunga range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewNickname Context triple: [Sandakphu, viewNickname, Sleeping Buddha view of Kanchenjunga range]
-
A.
trackNickname
Indicates that one entity is known or referred to by a particular nickname within the context of a track or recording.
-
B.
localNickname
Indicates that an entity is known by a particular nickname within a specific local or regional context.
-
C.
lineNickname
Indicates that one entity is an alternative or informal name (nickname) used to refer to a particular line (such as a route, service, or connection).
-
D.
nickNameGivenBy
Indicates that one entity assigns or uses a particular nickname for another entity.
-
E.
changedNicknameTo
Indicates that an entity has altered another entity’s nickname to a specified new nickname.
- F. None of above. chosen
Provenance (4 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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f627b403d0819083ef8ed23f802e35 |
completed | May 2, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 27, 2026, 11:28 a.m.