Triple
T11164431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burkes Garden, Virginia |
E264123
|
entity |
| Predicate | landformContext |
P80940
|
FINISHED |
| Object | karst-influenced valley |
—
|
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: karst-influenced valley | Statement: [Burkes Garden, Virginia, landformContext, karst-influenced valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landformContext Context triple: [Burkes Garden, Virginia, landformContext, karst-influenced valley]
-
A.
hasLandform
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
B.
topographicalCategory
chosen
Indicates the type of landform or surface feature that characterizes the physical terrain associated with an entity.
-
C.
landerType
Indicates the specific kind or category of lander involved in the relationship or action.
-
D.
connectsLandform
Indicates a relationship where one landform serves as a physical link or passage between two or more other landforms.
-
E.
geographicalNature
Indicates the natural geographic characteristics or physical landscape type associated with a place or region.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e887293081909830852000d533fa |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cec26fc8190a5497d186306f935 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.