Triple
T30753718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fehmarnbelt Tunnel |
E783022
|
entity |
| Predicate | hasSpecialElement |
P191359
|
FINISHED |
| Object | service element |
—
|
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: service element | Statement: [Fehmarnbelt Tunnel, hasSpecialElement, service element]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialElement Context triple: [Fehmarnbelt Tunnel, hasSpecialElement, service element]
-
A.
hasSpecial
Indicates that an entity possesses or is associated with a distinctive or exceptional attribute, status, or feature compared to others.
-
B.
hasNumberOfSpecials
Indicates that an entity is associated with a specific count of special items, features, or occurrences.
-
C.
hasSpecialBody
Indicates that an entity possesses a distinctive or non-standard physical form or body type compared to typical instances in its category.
-
D.
hasSpecials
Indicates that an entity offers or is associated with special deals, promotions, or limited-time offers.
-
E.
hasSpeculativeElement
Indicates that something includes a conjectural, hypothetical, or not-yet-verified component or aspect.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: April 29, 2026, 8:39 p.m.