Triple
T38601768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 41 in Indiana |
E934234
|
entity |
| Predicate | crossesStateLineFrom |
P185341
|
FINISHED |
| Object | Kentucky |
—
|
NE NERFINISHED |
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: Kentucky | Statement: [U.S. Route 41 in Indiana, crossesStateLineFrom, Kentucky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesStateLineFrom Context triple: [U.S. Route 41 in Indiana, crossesStateLineFrom, Kentucky]
-
A.
crossesStateBorders
chosen
Indicates that the referenced entity extends into or passes through more than one state’s territorial boundaries.
-
B.
crossesStateBoundaryViaBridgeTo
Indicates that one entity crosses a state boundary to reach another entity specifically by traveling over a bridge.
-
C.
crossesInternationalBoundaryAt
Indicates that one entity passes from one country’s territory into another at a specific boundary location.
-
D.
crossesBorderOf
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
-
E.
crossesCityLimit
Indicates that an entity moves from outside to inside, or inside to outside, the defined boundary of a city.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 3, 2026, 4:32 p.m.