Triple
T38624006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longhorn Cavern State Park |
E936953
|
entity |
| Predicate | CCCDevelopmentPeriod |
P22203
|
FINISHED |
| Object | 1930s |
—
|
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: 1930s | Statement: [Longhorn Cavern State Park, CCCDevelopmentPeriod, 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CCCDevelopmentPeriod Context triple: [Longhorn Cavern State Park, CCCDevelopmentPeriod, 1930s]
-
A.
mainDevelopmentPeriod
chosen
Indicates the primary time span during which the main development or formation of something took place.
-
B.
coDevelopedOrSupported
Indicates that two or more entities jointly developed or provided support for the same product, project, or initiative.
-
C.
developedUnder
Indicates that something was created, produced, or brought into existence while being subject to the authority, guidance, or conditions imposed by a particular person, organization, regime, or framework.
-
D.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
E.
hasDevelopmentStatus
Indicates the current stage or condition of progress or completion that something is in.
- 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.