Triple
T35234340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ash Cave |
E1017328
|
entity |
| Predicate | hasApproximateRecessDepth |
P9310
|
FINISHED |
| Object | about 100 feet |
—
|
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 feet | Statement: [Ash Cave, hasApproximateRecessDepth, about 100 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateRecessDepth Context triple: [Ash Cave, hasApproximateRecessDepth, about 100 feet]
-
A.
hasApproximateDepth
chosen
Indicates that an entity is associated with a depth value that is not exact but estimated or approximate.
-
B.
hasAverageDepth
Indicates that an entity possesses a specified mean depth value, typically measured over its entire extent or area.
-
C.
hasApproximateAverageThickness
Indicates that an entity possesses a thickness value that is an estimated or typical average rather than an exact measurement.
-
D.
hasRecessedSide
Indicates that one entity possesses a side or surface that is set back, indented, or recessed relative to its surrounding areas.
-
E.
hasDepth
Indicates that an entity possesses a measurable extent or distance from its surface inward or from top to bottom.
- 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: May 3, 2026, 4:02 p.m.