Triple
T7608532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky and Illinois |
E180172
|
entity |
| Predicate | areNeighboringStates |
P16236
|
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: [Kentucky and Illinois, areNeighboringStates, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areNeighboringStates Context triple: [Kentucky and Illinois, areNeighboringStates, true]
-
A.
hasNeighboringStateToWest
Indicates that one state is geographically located directly to the west of another state, sharing a common border.
-
B.
adjacentProvince
Indicates that two provinces share a common boundary and are directly next to each other geographically.
-
C.
borderingStateOrTerritory
chosen
Indicates that one state or territory shares a common boundary with another state or territory.
-
D.
memberStatesShareBorderAlong
Indicates that two member states have a common boundary running along a specified geographic feature or segment.
-
E.
nearbyState
Indicates that one state is geographically adjacent to or in close proximity to another state.
- 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_69c69f3567008190ab01d2ca7b53584a |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6fa1f6e888190ac6580724803fbc3 |
completed | March 27, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:54 p.m.