Triple
T33019467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scenic Rim volcanic region |
E844864
|
entity |
| Predicate | hasHighestPeakInRegion |
P197808
|
FINISHED |
| Object | Mount Barney |
—
|
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: Mount Barney | Statement: [Scenic Rim volcanic region, hasHighestPeakInRegion, Mount Barney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestPeakInRegion Context triple: [Scenic Rim volcanic region, hasHighestPeakInRegion, Mount Barney]
-
A.
nearHighestPeakOf
Indicates that one entity is located close to the highest peak of another referenced geographic or topographic feature.
-
B.
hasHighestPeakName
Indicates that the related value is the name of the tallest peak associated with the given entity.
-
C.
containsHighestPointOf
Indicates that one entity includes within its boundaries the location of the highest point of another entity.
-
D.
isMostFamousPeakOf
Indicates that one peak is recognized as the most famous or well-known peak associated with a particular geographic area, range, or entity.
-
E.
hasHighestPointAboveSeaLevel
Indicates that the highest point of one entity is located at a greater elevation above sea level than that of another entity.
- F. None of above. chosen
Provenance (4 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_69f3494f3b4081909dccf2af34372a26 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69feabcda59481908f2bc13b46fcced1 |
completed | May 9, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69feaabd63f88190b30dcf6dd2ea39d1 |
completed | May 9, 2026, 3:32 a.m. |
| PDg | Predicate description generation | batch_69feabcca6148190a8eb7b6fa33729c7 |
completed | May 9, 2026, 3:36 a.m. |
Created at: May 1, 2026, 1:23 a.m.