Triple
T13325128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Mountains sandstone vegetation communities |
E317419
|
entity |
| Predicate | associatedLandform |
P87992
|
FINISHED |
| Object | sandstone plateaus |
—
|
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: sandstone plateaus | Statement: [Blue Mountains sandstone vegetation communities, associatedLandform, sandstone plateaus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedLandform Context triple: [Blue Mountains sandstone vegetation communities, associatedLandform, sandstone plateaus]
-
A.
hasLandform
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
B.
associatedTopography
chosen
Indicates a relationship where one entity is linked or connected to a particular topographical feature or terrain.
-
C.
connectsLandform
Indicates a relationship where one landform serves as a physical link or passage between two or more other landforms.
-
D.
landerType
Indicates the specific kind or category of lander involved in the relationship or action.
-
E.
physicalFeature
Indicates that one entity possesses or exhibits a particular physical characteristic or attribute.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:30 p.m.