Triple
T13417451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maros Regency |
E313248
|
entity |
| Predicate | hasKarstTowerFormations |
P109828
|
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: [Maros Regency, hasKarstTowerFormations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKarstTowerFormations Context triple: [Maros Regency, hasKarstTowerFormations, yes]
-
A.
isKarstCave
Indicates that a cave is formed primarily through the dissolution of soluble rocks (such as limestone), characterizing it as a karst-type cave.
-
B.
hasSpeleothems
Indicates that a cave or subterranean space contains speleothems (mineral formations such as stalactites, stalagmites, or similar deposits).
-
C.
hasCaves
Indicates that one entity possesses, contains, or is characterized by the presence of caves.
-
D.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
E.
hasStateRockFormation
Indicates a relationship where a state is associated with or designated as having a particular rock formation.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaeb8416c8190a00dde0917c26f51 |
completed | April 12, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:39 p.m.