Triple
T38256176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammarsundet islands |
E1017798
|
entity |
| Predicate | hasStraitType |
P202721
|
FINISHED |
| Object | lake strait |
—
|
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: lake strait | Statement: [Hammarsundet islands, hasStraitType, lake strait]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStraitType Context triple: [Hammarsundet islands, hasStraitType, lake strait]
-
A.
hasStrait
Indicates that there is a strait—a narrow body of water—connecting or lying between the two referenced geographic entities.
-
B.
hasStrategicStrait
Indicates that one entity possesses or controls a strategically important narrow waterway that is relevant to another entity.
-
C.
locatedInStraitSystem
Indicates that one entity is situated within or along the geographic area of a particular strait system.
-
D.
locatedInStrait
Indicates that something is situated within or passes through a narrow body of water (a strait) that connects two larger bodies of water.
-
E.
hasKeyStrait
Indicates that one entity possesses or controls a strategically important strait that is crucial for access, passage, or connectivity to another entity.
- F. None of above. chosen
Provenance (4 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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00af6b3a948190a92813c13384c304 |
completed | May 10, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_6a00aec35610819085dd5137715a4228 |
completed | May 10, 2026, 4:13 p.m. |
| PDg | Predicate description generation | batch_6a00af6a5ffc819095c7331518a09f53 |
completed | May 10, 2026, 4:16 p.m. |
Created at: May 3, 2026, 4:30 p.m.