Triple
T7970468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WEB SLINGERS: A Spider-Man Adventure |
E185308
|
entity |
| Predicate | rideVehicleCapacity |
P24242
|
FINISHED |
| Object | 4 riders per vehicle |
—
|
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: 4 riders per vehicle | Statement: [WEB SLINGERS: A Spider-Man Adventure, rideVehicleCapacity, 4 riders per vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rideVehicleCapacity Context triple: [WEB SLINGERS: A Spider-Man Adventure, rideVehicleCapacity, 4 riders per vehicle]
-
A.
maximumPassengerCapacity
Indicates the greatest number of passengers that an entity is designed or allowed to carry at one time.
-
B.
numberOfRidersPerVehicle
chosen
Indicates the quantity of riders associated with each individual vehicle in the relationship.
-
C.
passengerCapacityCategory
Indicates the classification of an entity based on the number of passengers it is designed or allowed to carry.
-
D.
cargoCapacityFeature
Indicates that an entity has a feature specifying how much cargo it can carry or accommodate.
-
E.
hasBoatCapacity
Indicates the maximum number of people or amount of load that a boat is designed or allowed to carry.
- 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bd304dc8190b9feee5e17fc66db |
completed | March 31, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69cb047a8e4c81909b79e0f0bf56440c |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:13 p.m.