Triple
T32890209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederikssund Bridge |
E841309
|
entity |
| Predicate | hasClearanceForShips |
P90718
|
FINISHED |
| Object | limited, via bascule opening |
—
|
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: limited, via bascule opening | Statement: [Frederikssund Bridge, hasClearanceForShips, limited, via bascule opening]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClearanceForShips Context triple: [Frederikssund Bridge, hasClearanceForShips, limited, via bascule opening]
-
A.
supportsClassOfShip
Indicates that one entity is capable of accommodating, servicing, or otherwise functionally supporting a specified class of ship.
-
B.
appliesToShips
chosen
Indicates that the specified condition, rule, or attribute is relevant to or affects ships.
-
C.
isCapitalShip
Indicates that the subject vessel is classified as a capital ship, i.e., a primary, large, and heavily armed warship within a fleet.
-
D.
hasClearanceOver
Indicates that one entity possesses authorized access rights or control privileges over another entity or resource.
-
E.
hasShipRole
Indicates that an entity holds or is assigned a specific role or function on a ship.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 1, 2026, 1:18 a.m.