Triple
T26088709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Merc with a Mouth |
E658057
|
entity |
| Predicate | fandomNicknameFor |
P23575
|
FINISHED |
| Object | Deadpool |
—
|
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 | Statement: [The Merc with a Mouth, fandomNicknameFor, Deadpool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fandomNicknameFor Context triple: [The Merc with a Mouth, fandomNicknameFor, Deadpool]
-
A.
fandomNickname
chosen
Indicates that one entity is the nickname used by fans to refer to another entity (such as a person, group, or work).
-
B.
fandomIdentity
Indicates that an entity identifies as a fan or member of a particular fandom associated with another entity.
-
C.
fandomTerm
Indicates that one entity is a term, label, or piece of vocabulary specifically used within the fandom associated with another entity.
-
D.
fandomNameAssociation
Indicates an association between a fandom and the specific name used to refer to that fandom.
-
E.
fandomBase
Indicates that one entity serves as the primary fan community, origin, or core support base for 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60701aa94819095d95b71cb057622 |
completed | May 2, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:45 p.m.