Triple
T11668674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Fly |
E277317
|
entity |
| Predicate | hasSuperheroIdentityType |
P100683
|
FINISHED |
| Object | costumed crimefighter |
—
|
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: costumed crimefighter | Statement: [The Fly, hasSuperheroIdentityType, costumed crimefighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuperheroIdentityType Context triple: [The Fly, hasSuperheroIdentityType, costumed crimefighter]
-
A.
hasSecretIdentity
Indicates that an entity possesses an alternate, hidden identity that is not publicly known.
-
B.
knowsSecretIdentityOf
Indicates that one entity is aware of the hidden or private true identity of another entity.
-
C.
fatherSuperheroIdentity
Indicates that one entity is the father of another entity in the context of their superhero identities.
-
D.
hasSuperheroMantle
Indicates that one entity holds or has assumed the superhero identity, title, or role associated with another entity.
-
E.
appearsInIdentity
Indicates that an entity is featured, referenced, or plays a role within a particular identity or identity-related context.
- F. None of above. chosen
Provenance (4 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a440d8a481909a13c97813408bc8 |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d8938a1f8c81908ffb049fa5fee5a7 |
completed | April 10, 2026, 6:07 a.m. |
Created at: April 8, 2026, 9:39 p.m.