Triple
T38570144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parvati Wasatch |
E929241
|
entity |
| Predicate | usedAsCoverIdentity |
P114813
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Parvati Wasatch, usedAsCoverIdentity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsCoverIdentity Context triple: [Parvati Wasatch, usedAsCoverIdentity, yes]
-
A.
primaryCoverIdentity
Indicates that one entity serves as the main or principal cover identity used by another entity, typically for concealment or undercover purposes.
-
B.
usedBySuperheroIdentity
Indicates that a particular item, tool, or resource is utilized by a given superhero identity.
-
C.
characterCoverIdentity
chosen
Indicates that one character uses another identity as a cover or disguise, typically concealing their true identity.
-
D.
usedCover
Indicates that one entity employed another entity as a protective or concealing cover in a given context.
-
E.
usesSuperheroIdentity
Indicates that an entity adopts or operates under a superhero persona or alias, rather than their ordinary identity.
- 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 3, 2026, 4:32 p.m.