Triple
T390799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lehman Caves |
E8874
|
entity |
| Predicate | lengthApprox |
P266
|
FINISHED |
| Object | about 2 miles of mapped 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: about 2 miles of mapped passages | Statement: [Lehman Caves, lengthApprox, about 2 miles of mapped passages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lengthApprox Context triple: [Lehman Caves, lengthApprox, about 2 miles of mapped passages]
-
A.
length
chosen
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
B.
approximateSize
Indicates that one entity has a size that is roughly or approximately equal to the size of another entity.
-
C.
hasApproximateNumberOfLetters
Indicates that an entity is associated with a number that roughly, but not exactly, corresponds to the count of letters it contains.
-
D.
lengthInWords
Indicates the number of words that make up the length of something, typically a text or expression.
-
E.
hasApproximateDuration
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec5d73e881909101308a583c8f13 |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e96960608190bdd342da9c5ddb5e |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.