Triple
T25240921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pointe Young |
E632463
|
entity |
| Predicate | isSubsidiarySummitOf |
P71602
|
FINISHED |
| Object | Grandes Jorasses massif |
—
|
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: Grandes Jorasses massif | Statement: [Pointe Young, isSubsidiarySummitOf, Grandes Jorasses massif]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubsidiarySummitOf Context triple: [Pointe Young, isSubsidiarySummitOf, Grandes Jorasses massif]
-
A.
hasSubsummit
Indicates that one entity holds a subordinate or lower-ranked position under another entity within a hierarchical structure.
-
B.
coreSubsidiaryOf
Indicates that one entity is a primary or central subsidiary that is owned or controlled by another entity.
-
C.
isSecondarySummitOf
chosen
Indicates that one summit is a subsidiary or lesser peak that is topographically or hierarchically associated with a primary, higher summit.
-
D.
isSourceAndSummitOf
Indicates that an entity serves both as the originating point (source) and the highest point (summit) of another entity or feature.
-
E.
hasSummitIn
Indicates that an entity (such as a mountain or organization) has its summit or peak located within a specified place or region.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:07 p.m.