Triple
T27795791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinaya |
E701204
|
entity |
| Predicate | traditionalBaseFor |
P64725
|
FINISHED |
| Object | ascents of Mount Illimani |
—
|
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: ascents of Mount Illimani | Statement: [Pinaya, traditionalBaseFor, ascents of Mount Illimani]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalBaseFor Context triple: [Pinaya, traditionalBaseFor, ascents of Mount Illimani]
-
A.
traditionalBase
chosen
Indicates that one entity serves as the customary or historically established foundation or basis for another.
-
B.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
-
C.
traditionalBaseFabric
Indicates that one entity serves as the customary or historically used base fabric material for another entity.
-
D.
hasTraditionalBase
Indicates that something is supported by, built upon, or derived from an established traditional foundation or practice.
-
E.
establishedBase
Indicates that an entity has set up or founded a base or primary operational location in relation to another entity or place.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 27, 2026, 5:31 p.m.