Triple
T29870710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spider-Verse suit |
E758586
|
entity |
| Predicate | relatedSuit |
—
|
GENERATED |
| Object | Classic suit (Miles Morales) |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedSuit Context triple: [Spider-Verse suit, relatedSuit, Classic suit (Miles Morales)]
-
A.
relatedPass
Indicates that one pass is associated with or connected to another pass in some relevant way.
-
B.
relatedCase
Indicates that one legal case is connected or associated with another case, such as through shared facts, parties, issues, or procedural history.
-
C.
relatedCaseType
Indicates that one case is associated with another case through a specified type of relationship (e.g., precedent, reference, or dependency).
-
D.
relatedCorrespondence
Indicates that there exists a piece of correspondence (such as a letter, email, or message) that is associated with or pertains to the related entity.
-
E.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
- F. None of above. chosen
Provenance (1 batch)
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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:53 p.m.