Triple
T18898496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fish Rock |
E462271
|
entity |
| Predicate | hasCaveExitDepth |
P133717
|
FINISHED |
| Object | approximately 12 metres |
—
|
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: approximately 12 metres | Statement: [Fish Rock, hasCaveExitDepth, approximately 12 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaveExitDepth Context triple: [Fish Rock, hasCaveExitDepth, approximately 12 metres]
-
A.
hasNearbyCave
Indicates that one entity is located close to or in the vicinity of a cave associated with another entity.
-
B.
hasApproximateNumberOfCaves
Indicates that an entity is associated with an estimated or non-exact number of caves.
-
C.
hasCaves
Indicates that one entity possesses, contains, or is characterized by the presence of caves.
-
D.
hasLowerCave
Indicates that one location or structure possesses or is associated with another cave situated at a lower level or beneath it.
-
E.
caveNumber
Indicates a relationship where an entity is assigned or associated with a specific cave identifier or number.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c5277d788190a565794f7bd0e608 |
completed | April 20, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
| PDg | Predicate description generation | batch_69e4afa745c081908da20a51ebc147b4 |
completed | April 19, 2026, 10:34 a.m. |
Created at: April 10, 2026, 11:58 a.m.