Triple
T21383208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singletary Lake |
E527416
|
entity |
| Predicate | hasAssociatedLandform |
P940
|
FINISHED |
| Object | Carolina bay depression |
—
|
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: Carolina bay depression | Statement: [Singletary Lake, hasAssociatedLandform, Carolina bay depression]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedLandform Context triple: [Singletary Lake, hasAssociatedLandform, Carolina bay depression]
-
A.
hasLandform
chosen
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
B.
hasLandformOrigin
Indicates that something originates from, or is formed by, a particular landform.
-
C.
connectsLandform
Indicates a relationship where one landform serves as a physical link or passage between two or more other landforms.
-
D.
adjacentLandform
Indicates that two landforms are directly next to each other in space, sharing a common boundary or lying in immediate proximity.
-
E.
associatedTopography
Indicates a relationship where one entity is linked or connected to a particular topographical feature or terrain.
- 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_69e0b51f363c8190944000ab5523b02b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0f05278819096c511035ffc9777 |
completed | April 22, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:12 p.m.