Triple
T28422890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mao Asada |
E719988
|
entity |
| Predicate | performedElement |
P79011
|
FINISHED |
| Object | triple Axel in competition |
—
|
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: triple Axel in competition | Statement: [Mao Asada, performedElement, triple Axel in competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedElement Context triple: [Mao Asada, performedElement, triple Axel in competition]
-
A.
performedEvent
Indicates that an entity carried out, executed, or was responsible for a particular event.
-
B.
performedTo
Indicates that an action or performance is directed toward or carried out on a particular entity.
-
C.
performedWith
Indicates that an action or activity is carried out using, accompanied by, or in conjunction with a specified entity or instrument.
-
D.
hasPerformanceElement
chosen
Indicates that one entity includes, contains, or is associated with a specific performance-related component or element.
-
E.
performed
Indicates that an entity carried out, executed, or conducted a specific action, task, or activity.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 28, 2026, 1:34 a.m.