Triple
T31765164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sylt Shuttle |
E810785
|
entity |
| Predicate | hasAlternativeService |
P189452
|
FINISHED |
| Object | Autozug Sylt |
—
|
NE NERFINISHED |
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: Autozug Sylt | Statement: [Sylt Shuttle, hasAlternativeService, Autozug Sylt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeService Context triple: [Sylt Shuttle, hasAlternativeService, Autozug Sylt]
-
A.
hasAlternativeMedium
Indicates that an entity is available, expressed, or presented in another medium or format as an alternative to its primary one.
-
B.
hasAlternativeBearers
Indicates that an entity can be carried, represented, or borne by more than one possible bearer or carrier as alternatives.
-
C.
hasAlternativeProfile
Indicates that an entity is associated with another profile that serves as an alternative or secondary representation of it.
-
D.
hasAlternativeProgram
Indicates that one program is an alternative option or substitute for another program.
-
E.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: April 30, 2026, 11:32 p.m.