Triple
T7970467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WEB SLINGERS: A Spider-Man Adventure |
E185308
|
entity |
| Predicate | rideVehicle |
P63556
|
FINISHED |
| Object | WEB Slinger 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: WEB Slinger vehicle | Statement: [WEB SLINGERS: A Spider-Man Adventure, rideVehicle, WEB Slinger vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rideVehicle Context triple: [WEB SLINGERS: A Spider-Man Adventure, rideVehicle, WEB Slinger vehicle]
-
A.
canRideBy
Indicates that one entity is able to travel or move by means of another entity (such as a vehicle, animal, or transport mode).
-
B.
hasRideCycle
Indicates that one entity is associated with, or participates in, a recurring sequence or cycle of rides or ride operations.
-
C.
rideInteraction
chosen
Indicates an interaction where one entity is being transported or carried by another, typically by sitting or standing on or within it during movement.
-
D.
isRiddenBy
Indicates that an entity serves as a mount or vehicle that is being ridden by another entity.
-
E.
rideModel
Indicates that one entity is a specific model or type designation of a ride associated with another entity.
- 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.