Triple
T31425822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamburg, Iowa |
E801658
|
entity |
| Predicate | isInProximityToStateBorder |
P61305
|
FINISHED |
| Object | Iowa–Nebraska border |
—
|
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: Iowa–Nebraska border | Statement: [Hamburg, Iowa, isInProximityToStateBorder, Iowa–Nebraska border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInProximityToStateBorder Context triple: [Hamburg, Iowa, isInProximityToStateBorder, Iowa–Nebraska border]
-
A.
locatedNearStateBorderWith
chosen
Indicates that one entity is situated geographically close to the border of a specified state.
-
B.
borderStateNearby
Indicates that one state is geographically close to, but does not necessarily directly touch, the border of another state.
-
C.
nearStateBorderWith
Indicates that one entity is located close to the state border shared with another specified state or region.
-
D.
nearInternationalBoundary
Indicates that one entity is located close to an international boundary separating two or more countries.
-
E.
distanceToBorder
Indicates the measured or estimated spatial separation between a given entity or location and the nearest relevant border or boundary.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 8:52 p.m.