Triple
T15059792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winston Wolfe |
E379593
|
entity |
| Predicate | notableTraitInFandom |
P96545
|
FINISHED |
| Object | hyper-competence |
—
|
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: hyper-competence | Statement: [Winston Wolfe, notableTraitInFandom, hyper-competence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTraitInFandom Context triple: [Winston Wolfe, notableTraitInFandom, hyper-competence]
-
A.
notableTraitOnStage
Indicates that an entity is characterized by a distinctive or noteworthy trait specifically in the context of performing or appearing on stage.
-
B.
fandomCharacteristic
chosen
Indicates that an entity possesses a particular trait, behavior, or quality specifically in the context of its fandom or fan community.
-
C.
notableTraitInMarvel
Indicates that a particular trait or characteristic is especially prominent or noteworthy within the Marvel universe.
-
D.
notableCharacterType
Indicates that an entity is a notable or prominent example of a specified character type or role.
-
E.
notableFact
Indicates that there exists a particularly significant or noteworthy fact or piece of information associated with the subject.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dedee50afc8190bf7b0f4bbe8c60a3 |
completed | April 15, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:01 a.m.