Triple
T20861533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucerne–Immensee railway |
E513628
|
entity |
| Predicate | isImportantLinkIn |
P1887
|
FINISHED |
| Object | central Switzerland’s rail network |
—
|
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: central Switzerland’s rail network | Statement: [Lucerne–Immensee railway, isImportantLinkIn, central Switzerland’s rail network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isImportantLinkIn Context triple: [Lucerne–Immensee railway, isImportantLinkIn, central Switzerland’s rail network]
-
A.
isEssentialLinkFor
Indicates that one entity serves as a necessary or critical connection enabling or supporting another entity or process.
-
B.
isImportantFor
chosen
Indicates that something holds significant value, relevance, or necessity in relation to something else.
-
C.
isFixedLink
Indicates that there is a permanent, non-movable connection or linkage established between two entities.
-
D.
isMajorLinkBetween
Indicates that one entity serves as a primary or most significant connecting link between two or more other entities.
-
E.
hasExternalLink
Indicates that an entity is associated with a hyperlink pointing to a resource outside the current system or domain.
- 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3ad3d1c8190be2fe35a85f2447c |
completed | April 21, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:44 p.m.