Triple
T21410428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Taygetus |
E528152
|
entity |
| Predicate | highestPeakInstanceOf |
P210
|
FINISHED |
| Object | mountain summit |
—
|
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: mountain summit | Statement: [Mount Taygetus, highestPeakInstanceOf, mountain summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestPeakInstanceOf Context triple: [Mount Taygetus, highestPeakInstanceOf, mountain summit]
-
A.
highestPeakAccessible
Indicates that one location is the tallest peak that can be reached or accessed from another specified location or by a specified agent.
-
B.
highestPeakAccessed
Indicates that one entity has reached or visited the tallest peak associated with another entity or within a specified context.
-
C.
highestPoint
chosen
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
D.
hasHighestPointType
Indicates that the highest point of an entity is of a specified type or category.
-
E.
highestPeaksRelativeTo
Indicates a relationship where one location or region is associated with the tallest mountain peaks it contains, relative to surrounding areas or a defined reference set.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b1b4d4608190a86a6cd279709b21 |
completed | April 22, 2026, 11:32 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:42 p.m.