Triple
T38054055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirima National Park |
E949850
|
entity |
| Predicate | hasSandstoneFormations |
P192265
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mirima National Park, hasSandstoneFormations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSandstoneFormations Context triple: [Mirima National Park, hasSandstoneFormations, yes]
-
A.
hasKarstTowerFormations
Indicates that the subject possesses or contains karst tower landforms, typically steep or vertical limestone pillars formed by dissolution and erosion.
-
B.
hasStateRockFormation
Indicates a relationship where a state is associated with or designated as having a particular rock formation.
-
C.
hasNearbyRockFormation
Indicates that one entity is located close to or adjacent to a rock formation.
-
D.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
E.
hasMineralFeature
Indicates that one entity possesses, contains, or is characterized by a specific mineral-related feature or attribute.
- 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_69f76f000cf081908c11fb5443b392e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69fd026757a081909911a59a78652709 |
completed | May 7, 2026, 9:21 p.m. |
Created at: May 3, 2026, 4:20 p.m.