Triple
T30753733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fehmarnbelt Tunnel |
E783022
|
entity |
| Predicate | estimatedCostInBillionEUR |
P4259
|
FINISHED |
| Object | over 7 |
—
|
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: over 7 | Statement: [Fehmarnbelt Tunnel, estimatedCostInBillionEUR, over 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedCostInBillionEUR Context triple: [Fehmarnbelt Tunnel, estimatedCostInBillionEUR, over 7]
-
A.
economicDamageApprox
Indicates that one entity has caused or is associated with an estimated or approximate amount of economic damage to another entity or system.
-
B.
estimatedDevelopmentCostCurrency
Indicates the currency in which the estimated development cost is expressed.
-
C.
estimatedCost
chosen
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
-
D.
economicCost
Indicates the financial burden, expense, or resource expenditure associated with an action, event, or relationship between entities.
-
E.
acquisitionCost
Indicates the monetary amount or value required to obtain or purchase an 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 29, 2026, 8:39 p.m.