Triple
T21305446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okinoerabu Island |
E525184
|
entity |
| Predicate | hasKarstTopography |
P129309
|
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: [Okinoerabu Island, hasKarstTopography, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKarstTopography Context triple: [Okinoerabu Island, hasKarstTopography, 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.
isKarstCave
Indicates that a cave is formed primarily through the dissolution of soluble rocks (such as limestone), characterizing it as a karst-type cave.
-
C.
karstFeature
chosen
Indicates a relationship where a geographic entity is identified as, or associated with, a karst-related landform or feature formed by the dissolution of soluble rocks.
-
D.
hasMountainousTerrain
Indicates that a location or area possesses predominantly mountainous physical terrain or landscape features.
-
E.
hasLandform
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
- 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75aa3f90481909b212bdbf00c2bb0 |
completed | April 21, 2026, 11:08 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:05 p.m.