Triple
T33922662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mine |
E869655
|
entity |
| Predicate | hasNotableNaturalSite |
P66713
|
FINISHED |
| Object | Akiyoshidai karst plateau |
E1288101
|
NE 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: Akiyoshidai karst plateau | Statement: [Mine, hasNotableNaturalSite, Akiyoshidai karst plateau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableNaturalSite Context triple: [Mine, hasNotableNaturalSite, Akiyoshidai karst plateau]
-
A.
hasNotableNatureArea
chosen
Indicates that an entity possesses or is associated with a significant or noteworthy natural area.
-
B.
hasNotableNationalPark
Indicates that a place or region contains or is associated with a nationally recognized park of particular significance.
-
C.
hasNotableScenicSpot
Indicates that an entity possesses or is associated with a particularly remarkable or well-known scenic location.
-
D.
containsNaturalPark
Indicates that one entity geographically includes or encompasses a natural park within its boundaries.
-
E.
hasNaturalHeritage
Indicates that one entity possesses, is associated with, or includes natural heritage features or values (such as landscapes, ecosystems, or natural sites) related to another entity.
- F. None of above.
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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0224f4b6cc8190a8f79700a9af765f |
completed | May 11, 2026, 6:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a368253d3f081909ba6e5e21837c1b7 |
completed | June 20, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_6a0223f01eb081909419518fdd45f2a4 |
completed | May 11, 2026, 6:46 p.m. |
Created at: May 1, 2026, 1:49 a.m.