Triple
T25598882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grotta Gigante |
E641730
|
entity |
| Predicate | hasCaveDepth |
P43725
|
FINISHED |
| Object | about 100 m below surface |
—
|
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: about 100 m below surface | Statement: [Grotta Gigante, hasCaveDepth, about 100 m below surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaveDepth Context triple: [Grotta Gigante, hasCaveDepth, about 100 m below surface]
-
A.
hasCaveEntranceDepth
Indicates the depth or vertical distance of a cave’s entrance relative to a reference level (such as ground surface or sea level).
-
B.
hasCaveExitDepth
Indicates the depth at which a cave’s exit is located relative to a defined reference level.
-
C.
hasUndergroundDepth
chosen
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
D.
hasApproximateNumberOfCaves
Indicates that an entity is associated with an estimated or non-exact number of caves.
-
E.
hasLowerCave
Indicates that one location or structure possesses or is associated with another cave situated at a lower level or beneath it.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 21, 2026, 4:30 p.m.