Triple
T26928270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Little Belt Bridge |
E678142
|
entity |
| Predicate | isOnStrait |
P71311
|
FINISHED |
| Object | Little Belt strait |
—
|
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: Little Belt strait | Statement: [New Little Belt Bridge, isOnStrait, Little Belt strait]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnStrait Context triple: [New Little Belt Bridge, isOnStrait, Little Belt strait]
-
A.
hasStrait
Indicates that there is a strait—a narrow body of water—connecting or lying between the two referenced geographic entities.
-
B.
isMostlyStraight
Indicates that an entity is predominantly but not entirely straight in orientation, alignment, or form.
-
C.
isInlandRoute
Indicates that a route runs through inland areas rather than along the coast or over open water.
-
D.
locatedInStrait
chosen
Indicates that something is situated within or passes through a narrow body of water (a strait) that connects two larger bodies of water.
-
E.
isOnEastWestTrunkLine
Indicates that something is located on, or directly aligned with, a primary east–west transportation or utility trunk line.
- 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62013a6348190bd1b5a8eed5c3e82 |
completed | May 2, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:11 a.m.