Triple
T36317438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New River (South Carolina) |
E894236
|
entity |
| Predicate | hasCountyOnBank |
P142266
|
FINISHED |
| Object | Jasper County, South Carolina |
E257755
|
NE 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: Jasper County, South Carolina | Statement: [New River (South Carolina), hasCountyOnBank, Jasper County, South Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountyOnBank Context triple: [New River (South Carolina), hasCountyOnBank, Jasper County, South Carolina]
-
A.
hasDistrictOnBanks
Indicates that a district is located along or adjacent to the banks of a river or similar water body.
-
B.
hasBankOn
chosen
Indicates that one entity is located on or alongside the bank (edge) of another entity, typically a river, lake, or similar body.
-
C.
hasProvinceOnBank
Indicates that a province is located along or adjacent to the bank of a specified body of water.
-
D.
hasCountyCode
Indicates that an entity is associated with a specific county identified by a standardized county code.
-
E.
hasRankInCounty
Indicates that an entity holds a specific rank or position within the administrative boundaries of a particular county.
- F. None of above.
Provenance (4 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_69f76e4d1a788190a6ab6ccca28547a7 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e8c1749148190994a168e5329e623 |
completed | June 26, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.