Triple
T32606735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marvel Team-Up |
E833539
|
entity |
| Predicate | teamUpFormat |
P78540
|
FINISHED |
| Object | Spider-Man plus one guest hero |
—
|
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: Spider-Man plus one guest hero | Statement: [Marvel Team-Up, teamUpFormat, Spider-Man plus one guest hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamUpFormat Context triple: [Marvel Team-Up, teamUpFormat, Spider-Man plus one guest hero]
-
A.
teamUpWith
Indicates forming a cooperative partnership or alliance with another entity to work together toward a shared goal.
-
B.
teamFormat
chosen
Indicates the structural arrangement or configuration in which a team is organized or operates.
-
C.
teamSizeFormat
Indicates how the size of a team is represented or formatted (e.g., as a number, range, or categorized label).
-
D.
teamBasedOn
Indicates that one entity (typically a team) is formed, organized, or defined on the basis of another entity (such as a criterion, source, or underlying structure).
-
E.
teamSizeVariantOf
Indicates that one entity represents a variation of another entity specifically in terms of team size configuration or composition.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c6c719488190b91df99a88a5119b |
completed | May 3, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:05 a.m.