Triple
T30202865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Gee County |
E767830
|
entity |
| Predicate | borderInternalDivision |
P88527
|
FINISHED |
| Object | Grand Gedeh County |
—
|
NE NERFINISHED |
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: Grand Gedeh County | Statement: [River Gee County, borderInternalDivision, Grand Gedeh County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderInternalDivision Context triple: [River Gee County, borderInternalDivision, Grand Gedeh County]
-
A.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
-
B.
bordersInternalDivision
chosen
Indicates that one administrative or internal division shares a common boundary with another internal division within the same larger entity.
-
C.
borderSectionOf
Indicates that one entity represents a specific segment or portion of the overall border of another entity.
-
D.
borderDistribution
Indicates how a boundary or border is spatially arranged, divided, or allocated between adjacent entities.
-
E.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
- 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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: April 29, 2026, 7:31 p.m.