Triple
T29571991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rendsburg ferry |
E753337
|
entity |
| Predicate | serviceResumption |
P51446
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Rendsburg ferry, serviceResumption, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceResumption Context triple: [Rendsburg ferry, serviceResumption, 2019]
-
A.
serviceResumed
chosen
Indicates that a previously interrupted or suspended service has been restarted and is functioning again.
-
B.
serviceContinuityWith
Indicates that one service ensures or supports the uninterrupted operation or seamless transition of another service.
-
C.
serviceDuring
Indicates that one entity performs or provides a service for another entity during a specified time period or event.
-
D.
service
Indicates that one entity performs work, assistance, or functions to meet the needs or requests of another entity.
-
E.
serviceSystem
Indicates a relationship where one entity functions as a service system that provides, manages, or supports services for another 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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 28, 2026, 5:59 p.m.