Triple
T21216339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulugh Muztagh |
E522844
|
entity |
| Predicate | typeOfRock |
P1326
|
FINISHED |
| Object | mainly metamorphic and sedimentary rocks |
—
|
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: mainly metamorphic and sedimentary rocks | Statement: [Ulugh Muztagh, typeOfRock, mainly metamorphic and sedimentary rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRock Context triple: [Ulugh Muztagh, typeOfRock, mainly metamorphic and sedimentary rocks]
-
A.
hasRockType
chosen
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
B.
rockTypeMarketedAs
Indicates that a particular rock type is promoted or advertised under a specific commercial or trade name.
-
C.
geologicType
Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
-
D.
climbingRockType
Indicates that an entity is associated with or characterized by a particular type of rock used or encountered in climbing activities.
-
E.
centralRockName
Indicates that an entity has a specific name assigned to its central rock or primary rock feature.
- 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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73473870c8190a0f41f9c85567aa7 |
completed | April 21, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:41 p.m.