Triple
T19684693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tasman National Park |
E472681
|
entity |
| Predicate | hasHighestCliffs |
P78994
|
FINISHED |
| Object | some of the highest sea cliffs in Australia |
—
|
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: some of the highest sea cliffs in Australia | Statement: [Tasman National Park, hasHighestCliffs, some of the highest sea cliffs in Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestCliffs Context triple: [Tasman National Park, hasHighestCliffs, some of the highest sea cliffs in Australia]
-
A.
hasCliffsOn
Indicates that one entity possesses or features cliffs located along or on the surface of another entity.
-
B.
hasCliffs
Indicates that something possesses or is characterized by the presence of cliffs.
-
C.
containsHighestPointOf
Indicates that one entity includes within its boundaries the location of the highest point of another entity.
-
D.
hasHighestPeaksOver
Indicates that one entity possesses mountain peaks that are higher in elevation than those of another entity.
-
E.
hasHighestSeaCliffsNearby
chosen
Indicates that an entity is located near, or associated with, the area containing the tallest sea cliffs in a given 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641c225fc81909637d304891f4abd |
completed | April 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.