Triple
T5070171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain Underpants |
E114256
|
entity |
| Predicate | transformationTrigger |
P58568
|
FINISHED |
| Object | hypnosis |
—
|
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: hypnosis | Statement: [Captain Underpants, transformationTrigger, hypnosis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transformationTrigger Context triple: [Captain Underpants, transformationTrigger, hypnosis]
-
A.
transformedDuring
Indicates that an entity undergoes a change in form, state, or structure within the duration of a specified event or process.
-
B.
triggeredFrom
Indicates that one event, action, or process was initiated or caused as a result of another specific event, action, or process.
-
C.
trigger
chosen
Indicates that one entity causes or initiates an event, state, or action in another entity or system.
-
D.
transformationProperty
Indicates that one entity has a specific behavior, constraint, or characteristic related to how it changes, converts, or is transformed into another form or state.
-
E.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
- 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_69bd443cf28c8190ad371d603563dbdd |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd749f47908190891ac8432c5b5615 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.