Triple
T6230988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regionalbahn |
E139350
|
entity |
| Predicate | luggagePolicy |
P38285
|
FINISHED |
| Object | allows hand luggage |
—
|
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: allows hand luggage | Statement: [Regionalbahn, luggagePolicy, allows hand luggage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: luggagePolicy Context triple: [Regionalbahn, luggagePolicy, allows hand luggage]
-
A.
baggagePolicyType
chosen
Indicates the specific category or type of baggage policy that applies in a given travel or transportation context.
-
B.
baggagePolicySetBy
Indicates that a specific baggage policy is determined, defined, or controlled by a particular entity (such as an airline or service provider).
-
C.
hasBaggageClaim
Indicates that a location, typically a transportation hub, includes or provides a baggage claim area for retrieving luggage.
-
D.
hasBaggageCheck
Indicates that an entity provides or is associated with a service or facility for checking in baggage.
-
E.
baggageAllowanceComparedToPremiumCabins
Indicates how a passenger’s baggage allowance compares in quantity or weight to that granted in premium cabin classes.
- 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_69c008afd3148190b71e9eaa60420dd1 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062ec5be4819084d6df2e8dd2a542 |
completed | March 22, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69c05601de6481909d0880048fd7b49a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:22 p.m.