Triple
T8082191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illinois and Indiana |
E188641
|
entity |
| Predicate | sharesBorderDefinedBy |
P43209
|
FINISHED |
| Object | surveyed meridians and parallels |
—
|
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: surveyed meridians and parallels | Statement: [Illinois and Indiana, sharesBorderDefinedBy, surveyed meridians and parallels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesBorderDefinedBy Context triple: [Illinois and Indiana, sharesBorderDefinedBy, surveyed meridians and parallels]
-
A.
sharesBorderType
Indicates that two entities are connected by a common boundary characterized by the same specified type of border (e.g., land, river, maritime).
-
B.
borderDefinedBy
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
-
C.
relatedBorder
chosen
Indicates that two geographic or political entities share a common boundary or border with each other.
-
D.
shareNotableBorderRegion
Indicates that two entities share a common border in a region that is particularly significant or notable (e.g., historically, politically, or geographically).
-
E.
borderedBy
Indicates that one entity shares a common boundary or edge 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_69ca82b662e88190b9323daab8c28a21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb40a699388190a5b8e26524ae43e5 |
completed | March 31, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69cb049f1614819087360d1a4c6f0faa |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:28 p.m.