Triple
T30846121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Organ Cave |
E785637
|
entity |
| Predicate | hasSurveyedLength |
P158235
|
FINISHED |
| Object | over 40 miles |
—
|
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 40 miles | Statement: [Organ Cave, hasSurveyedLength, over 40 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurveyedLength Context triple: [Organ Cave, hasSurveyedLength, over 40 miles]
-
A.
surveyedLength
chosen
Indicates the measured extent or distance of something as determined through a surveying process.
-
B.
surveyedFor
Indicates that one entity has been examined, questioned, or assessed in order to gather information specifically about another entity or topic.
-
C.
surveyedIn
Indicates that an entity was included as part of the scope or coverage of a particular survey or data-collection effort.
-
D.
usesSurveyOf
Indicates that one entity bases its work, analysis, or decision on data or findings obtained from a particular survey conducted by another entity.
-
E.
hasSurveyRole
Indicates that an entity holds a specific role or responsibility within the context of a survey.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: April 29, 2026, 8:46 p.m.