Triple
T16850764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Escarpment of eastern Australia |
E409668
|
entity |
| Predicate | hasMaximumReliefUpTo |
P96664
|
FINISHED |
| Object | about 1000 metres |
—
|
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: about 1000 metres | Statement: [Great Escarpment of eastern Australia, hasMaximumReliefUpTo, about 1000 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumReliefUpTo Context triple: [Great Escarpment of eastern Australia, hasMaximumReliefUpTo, about 1000 metres]
-
A.
hasRelativeRelief
Indicates a relationship where one entity is characterized by the degree of variation in elevation or relief relative to another reference entity or area.
-
B.
hasReliefRange
chosen
Indicates a relationship where an entity is associated with a specified range or interval of relief (e.g., elevation difference or surface variation) values.
-
C.
hasTopElevation
Indicates that an entity has a specified maximum or highest elevation value.
-
D.
hasReliefFeature
Indicates that one entity possesses or includes a specific relief-related physical feature or characteristic.
-
E.
hasMaxDisplacement
Indicates the maximum distance or extent to which something can move or be displaced from its original position.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b378dda48190ab81d75f2cfe3ab3 |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.