Triple
T38482193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Flying Tomato |
E915708
|
entity |
| Predicate | associatedWithTrickType |
P50989
|
FINISHED |
| Object | aerial tricks |
—
|
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: aerial tricks | Statement: [The Flying Tomato, associatedWithTrickType, aerial tricks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithTrickType Context triple: [The Flying Tomato, associatedWithTrickType, aerial tricks]
-
A.
hasTrickType
chosen
Indicates that an entity (such as a trick or maneuver) is associated with a specific type or category of trick.
-
B.
associatedWithGimmick
Indicates that one entity is connected or linked to a particular gimmick, typically as a defining feature, strategy, or promotional element.
-
C.
performedTrick
Indicates that one entity executed or carried out a trick involving another entity or in a particular context.
-
D.
associatedWithTaunt
Indicates that one entity is linked to, involved in, or characterized by a taunt directed at another entity.
-
E.
hasTrapeze
Indicates that one entity possesses, includes, or is equipped with a trapeze.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.