Triple
T38624012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longhorn Cavern State Park |
E936953
|
entity |
| Predicate | caveLength |
P68979
|
FINISHED |
| Object | over 1 mile of developed passages |
—
|
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: over 1 mile of developed passages | Statement: [Longhorn Cavern State Park, caveLength, over 1 mile of developed passages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caveLength Context triple: [Longhorn Cavern State Park, caveLength, over 1 mile of developed passages]
-
A.
undergroundCavernLength
chosen
Indicates the measured linear extent or distance from one end to the other of an underground cavern.
-
B.
caveNumber
Indicates a relationship where an entity is assigned or associated with a specific cave identifier or number.
-
C.
undergroundCavernWidth
Indicates the horizontal extent or span of an underground cavern from one side to the other.
-
D.
hasApproximateNumberOfCaves
Indicates that an entity is associated with an estimated or non-exact number of caves.
-
E.
caveSystem
Indicates that one entity is a cave system that contains or connects multiple subterranean spaces relative to another entity.
- 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.