Triple
T26490253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limfjord Railway Bridge |
E669135
|
entity |
| Predicate | designedToOpenFor |
P96898
|
FINISHED |
| Object | ship traffic |
—
|
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: ship traffic | Statement: [Limfjord Railway Bridge, designedToOpenFor, ship traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToOpenFor Context triple: [Limfjord Railway Bridge, designedToOpenFor, ship traffic]
-
A.
canBeOpenedBy
Indicates that one entity has the ability or permission to open another entity.
-
B.
intendedOpeningUse
chosen
Indicates that an opening (such as a door, window, or passage) is designed or meant to be used for a particular purpose or function.
-
C.
openedForUseBy
Indicates that something has been made available or activated so that a particular entity can use it.
-
D.
hasClearanceWhenOpen
Indicates that an entity possesses the required clearance or authorization specifically during the time or condition when something (e.g., a resource, facility, or system) is open or accessible.
-
E.
hasOpenedFor
Indicates that one entity has performed or appeared as the opening act or preliminary participant for another entity, typically in an event or performance context.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 27, 2026, 1:03 a.m.