Triple
T11669557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master Man |
E277341
|
entity |
| Predicate | enhancementType |
P14379
|
FINISHED |
| Object | super-soldier serum variant |
—
|
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: super-soldier serum variant | Statement: [Master Man, enhancementType, super-soldier serum variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enhancementType Context triple: [Master Man, enhancementType, super-soldier serum variant]
-
A.
enhancedBy
Indicates that one entity’s value, effectiveness, or impact is increased or improved as a result of another entity.
-
B.
boosterType
chosen
Indicates the specific kind or category of booster associated with an entity or action.
-
C.
extensionType
Indicates the specific kind or category of extension that characterizes how something is extended or augmented beyond its base form.
-
D.
adjustmentType
Indicates the specific kind or category of modification applied to an existing value, state, or configuration within the relationship.
-
E.
phase2Enhancement
Indicates that an entity is involved in or associated with the second phase of an enhancement or improvement process.
- 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_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. |
Created at: April 8, 2026, 9:39 p.m.