Triple
T26873619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lillebælt |
E676682
|
entity |
| Predicate | hasNotableBridgeOpeningYear |
P47616
|
FINISHED |
| Object | 1935 for Old Little Belt Bridge |
—
|
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: 1935 for Old Little Belt Bridge | Statement: [Lillebælt, hasNotableBridgeOpeningYear, 1935 for Old Little Belt Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableBridgeOpeningYear Context triple: [Lillebælt, hasNotableBridgeOpeningYear, 1935 for Old Little Belt Bridge]
-
A.
originalBridgeOpened
Indicates that the first or initial version of a bridge was opened for use or put into operation.
-
B.
openedHistoricBridgeTo
Indicates that an entity initiated public access or use of a bridge recognized as historic.
-
C.
bridgeOpened
chosen
Indicates that a bridge has transitioned from a closed or inactive state to being open and available for use.
-
D.
hasBridges
Indicates that one entity possesses, contains, or is characterized by one or more bridges connecting locations or components.
-
E.
hasNumberOfBridges
Indicates the quantitative relationship specifying how many bridges are associated with a given entity.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: April 27, 2026, 5:34 a.m.