Triple
T36317347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grahamville, South Carolina |
E894233
|
entity |
| Predicate | typicalCountySeat |
P383
|
FINISHED |
| Object | Ridgeland, South Carolina |
E915800
|
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: Ridgeland, South Carolina | Statement: [Grahamville, South Carolina, typicalCountySeat, Ridgeland, South Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCountySeat Context triple: [Grahamville, South Carolina, typicalCountySeat, Ridgeland, South Carolina]
-
A.
hasCountySeatOf
Indicates that a place serves as the administrative county seat (capital) of a specified county.
-
B.
containsCountySeat
Indicates that one administrative region or area includes within its boundaries the designated county seat location of a county.
-
C.
nearestCountySeat
Indicates that one location is the closest county seat geographically to another location.
-
D.
hasCountySeatCounty
Indicates that a county seat is administratively associated with and serves as the seat of government for a specific county.
-
E.
countySeat
chosen
Indicates that one place serves as the administrative center or capital of a 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_6a39a3186f008190bcbe76eaba55401a |
completed | June 22, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.