Triple
T17617068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanga Parbat |
E429110
|
entity |
| Predicate | RupalFaceClaim |
P125774
|
FINISHED |
| Object | one of the highest mountain faces in the world |
—
|
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: one of the highest mountain faces in the world | Statement: [Nanga Parbat, RupalFaceClaim, one of the highest mountain faces in the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RupalFaceClaim Context triple: [Nanga Parbat, RupalFaceClaim, one of the highest mountain faces in the world]
-
A.
recordClaim
Indicates that an entity formally documents or logs a claim made by another entity or about a particular matter.
-
B.
facesChallenge
Indicates that an entity is confronted with a difficulty, obstacle, or demanding situation that must be dealt with or overcome.
-
C.
labelClaim
chosen
Indicates that an entity asserts or assigns a specific label or classification to another entity or statement.
-
D.
usedToClaim
Indicates that something is employed as evidence, justification, or support in making a particular claim.
-
E.
challengesClaim
Indicates that one entity disputes, questions, or opposes the validity or correctness of another entity’s claim.
- F. None of above.
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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d33a2b081908deecee773c333af |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.