Triple
T25196633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pointe Whymper |
E631016
|
entity |
| Predicate | includedInListing |
P31874
|
FINISHED |
| Object | Alpine mountains above 4000 m |
—
|
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: Alpine mountains above 4000 m | Statement: [Pointe Whymper, includedInListing, Alpine mountains above 4000 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedInListing Context triple: [Pointe Whymper, includedInListing, Alpine mountains above 4000 m]
-
A.
usedInCatalogue
Indicates that something is included or referenced as an entry within a catalogue.
-
B.
usedInECommerce
Indicates that something is employed or applied within the context of electronic commerce activities or systems.
-
C.
usedInPriceTags
Indicates that something is employed or referenced in the creation, display, or calculation of price tags.
-
D.
includedInEdition
Indicates that one item (such as a work, text, or component) is contained within or forms part of a particular edition.
-
E.
listedWith
chosen
Indicates that an entity is included as an item or entry within a particular list, catalog, or collection.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 21, 2026, 12:50 p.m.