Triple
T24204896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hugh Morrus |
E600077
|
entity |
| Predicate | signatureMoveType |
P108696
|
FINISHED |
| Object | moonsault |
—
|
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: moonsault | Statement: [Hugh Morrus, signatureMoveType, moonsault]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureMoveType Context triple: [Hugh Morrus, signatureMoveType, moonsault]
-
A.
signatureType
Indicates the specific kind or category of a signature associated with an entity or action.
-
B.
signType
Indicates the specific category or kind of sign involved in the relationship or action.
-
C.
signatureWorkType
Indicates the specific category or type of work that serves as a defining or primary example associated with an entity.
-
D.
usesSignatureMove
chosen
Indicates that an entity performs or employs a distinctive, characteristic move or technique associated specifically with it.
-
E.
signatoryType
Indicates the specific role or category of a party that has signed or formally agreed to a document, contract, or agreement.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca52cb881908c99913ea93bc88e |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:37 p.m.