Triple
T11976267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bride Peak |
E285047
|
entity |
| Predicate | isInPakistan |
P102671
|
FINISHED |
| Object | true |
—
|
LITERAL 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: true | Statement: [Bride Peak, isInPakistan, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInPakistan Context triple: [Bride Peak, isInPakistan, true]
-
A.
statusInPakistan
Indicates the legal, social, or operational condition or standing that something or someone has within the context of Pakistan.
-
B.
areaRankInPakistan
Indicates the relative position of an entity when all entities in Pakistan are ordered by their area size.
-
C.
returnedToPakistan
Indicates that an entity went back to Pakistan after having been away.
-
D.
PakistaniResponse
Indicates a response, reaction, or action taken by Pakistan or Pakistani authorities in relation to a preceding event, request, or situation.
-
E.
legalStatusAccordingToChinaAndPakistan
Indicates the legal status or classification of something as defined or recognized jointly by the laws or official positions of China and Pakistan.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903acbb9081908fe7f8360057785c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d903a8695c8190bfa9d7ca50834f9f |
completed | April 10, 2026, 2:05 p.m. |
Created at: April 8, 2026, 9:46 p.m.