Triple
T28794140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koblenz cable car over Rhine |
E727039
|
entity |
| Predicate | maximumCapacityPerCabin |
P11680
|
FINISHED |
| Object | 35 passengers |
—
|
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: 35 passengers | Statement: [Koblenz cable car over Rhine, maximumCapacityPerCabin, 35 passengers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumCapacityPerCabin Context triple: [Koblenz cable car over Rhine, maximumCapacityPerCabin, 35 passengers]
-
A.
maximumPassengerCapacity
chosen
Indicates the greatest number of passengers that an entity is designed or allowed to carry at one time.
-
B.
seatingCapacity
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
C.
passengerCapacityCategory
Indicates the classification of an entity based on the number of passengers it is designed or allowed to carry.
-
D.
additionalEmbarkedPersonnelCapacity
Indicates the maximum number of extra personnel that can be taken on board beyond the standard embarked complement.
-
E.
hasCrewCapacity
Indicates that an entity is capable of accommodating a specified number of crew members.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 28, 2026, 6:24 a.m.