Triple
T23237735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delmar, Delaware |
E581348
|
entity |
| Predicate | straddlesBoundaryType |
P1589
|
FINISHED |
| Object | state line |
—
|
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: state line | Statement: [Delmar, Delaware, straddlesBoundaryType, state line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: straddlesBoundaryType Context triple: [Delmar, Delaware, straddlesBoundaryType, state line]
-
A.
hasBoundaryType
Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
-
B.
borderStraddling
chosen
Indicates that something (such as a feature, structure, or area) extends across and occupies territory on both sides of a border between two regions or jurisdictions.
-
C.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
D.
boundaryCurrentType
Indicates the specific kind or classification of the current that exists at or across a boundary between regions or components.
-
E.
stateBoundaryBetween
Indicates a boundary line that separates or lies between two states.
- 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192ea590c81908cd677d89f67d49f |
completed | April 29, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:09 p.m.