Triple
T3929175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alabama–Mississippi border |
E93351
|
entity |
| Predicate | hasPoliticalSubdivisionOnEast |
P51741
|
FINISHED |
| Object | counties of Alabama |
—
|
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: counties of Alabama | Statement: [Alabama–Mississippi border, hasPoliticalSubdivisionOnEast, counties of Alabama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoliticalSubdivisionOnEast Context triple: [Alabama–Mississippi border, hasPoliticalSubdivisionOnEast, counties of Alabama]
-
A.
governingCountryOnEast
Indicates that a country exercises governmental authority or control over a territory or region located to its east.
-
B.
easternmostPartOf
Indicates that one entity is the geographically furthest-east portion or segment of another entity.
-
C.
locatedEastOf
Indicates that one entity is positioned geographically to the east of another entity.
-
D.
easternPartOccupiedBy
Indicates that the eastern portion of a region, area, or object is taken up, inhabited, or used by a specified entity.
-
E.
locatedInEasternPartOf
Indicates that one entity is situated within the eastern portion or region of another entity.
- F. None of above. chosen
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_69aed96bfa1081908f7b30f2c647dee6 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeeda65b708190b24cd715915aec1d |
completed | March 9, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69aee7609c4081908000ce12ae827c3f |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeeb5f859c819095b61f5ba8eace4f |
completed | March 9, 2026, 3:46 p.m. |
Created at: March 9, 2026, 3:23 p.m.