Triple
T5001264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SBB Immobilien |
E112376
|
entity |
| Predicate | commercializes |
P3849
|
FINISHED |
| Object | retail space in stations |
—
|
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: retail space in stations | Statement: [SBB Immobilien, commercializes, retail space in stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercializes Context triple: [SBB Immobilien, commercializes, retail space in stations]
-
A.
commercialized
Indicates that something has been developed, marketed, or exploited for profit in a commercial context.
-
B.
commercializedIn
Indicates that something has been brought to market or made available for commercial sale or use within a specified place or context.
-
C.
commercial
chosen
Indicates that one entity is engaged in a business-related or profit-oriented relationship, activity, or transaction with another entity.
-
D.
commercialAccess
Indicates that an entity is permitted to use or access something for commercial or profit-generating purposes.
-
E.
commercialActivity
Indicates an action or relationship involving the buying, selling, or exchange of goods or services for profit or other economic gain.
- 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_69bd4432b32c81909f3b3c6bd10f0653 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7472a1dc8190942f568a81fdd961 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd714aee2481908fb0dd5fa2daf3a1 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:34 p.m.