Triple
T26088861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deadpool Corps |
E658061
|
entity |
| Predicate | memberOfTeamVariant |
P19122
|
FINISHED |
| Object | Deadpool Corps: Rank and Foul |
—
|
NE NERFINISHED |
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: Deadpool Corps: Rank and Foul | Statement: [Deadpool Corps, memberOfTeamVariant, Deadpool Corps: Rank and Foul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberOfTeamVariant Context triple: [Deadpool Corps, memberOfTeamVariant, Deadpool Corps: Rank and Foul]
-
A.
hasVariantTeam
Indicates that one team is an alternative or variant form of another team within the same context or structure.
-
B.
hasTeamMember
Indicates that an entity includes another entity as a member of its team.
-
C.
includesTeam
Indicates that a group, project, or organization has a specific team as one of its constituent members or components.
-
D.
memberTeam
chosen
Indicates that an entity belongs to or is part of a specific team.
-
E.
hasTeamFor
Indicates that an entity possesses, is associated with, or is responsible for a specific team designated for a particular purpose or context.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 26, 2026, 7:45 p.m.