Triple
T23622402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town of Six Mile, South Carolina |
E583355
|
entity |
| Predicate | isInMountainFoothills |
P138580
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Town of Six Mile, South Carolina, isInMountainFoothills, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInMountainFoothills Context triple: [Town of Six Mile, South Carolina, isInMountainFoothills, true]
-
A.
locatedInMountain
Indicates that something is situated within, on, or as part of a mountain.
-
B.
isInValleyOrMountainRegion
Indicates that an entity is located within either a valley area or a mountainous region.
-
C.
locatedInMountainRangeRegion
Indicates that a place or geographic entity is situated within the area covered by a specific mountain range.
-
D.
hasFoothillsOn
chosen
Indicates that one geographic feature is situated at or along the lower slopes or foothills of another, typically larger, landform such as a mountain or mountain range.
-
E.
isOnHill
Indicates that one entity is located on or atop a hill relative to another reference frame or context.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b179ebf48190a34ad0d3ddf0e103 |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:46 p.m.