Triple
T4284423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quincy, Illinois |
E97230
|
entity |
| Predicate | borderRelationship |
P37800
|
FINISHED |
| Object | across the Mississippi River from Missouri |
—
|
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: across the Mississippi River from Missouri | Statement: [Quincy, Illinois, borderRelationship, across the Mississippi River from Missouri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderRelationship Context triple: [Quincy, Illinois, borderRelationship, across the Mississippi River from Missouri]
-
A.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
B.
relatedBorder
Indicates that two geographic or political entities share a common boundary or border with each other.
-
C.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
D.
borderConcern
Indicates a relationship where one entity has issues, disputes, or security considerations related to its shared boundary or border with another entity.
-
E.
hasBorderRelation
chosen
Indicates that one entity shares a boundary or border with another entity.
- 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_69b3454595848190a0e6bbb6a2bea040 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3503c062c81908f9a9eeab5381ec9 |
completed | March 12, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69b347fc4c0c8190a7fcd814e27308a5 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.