Triple
T7756916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catch wrestling |
E175920
|
entity |
| Predicate | hasNotableTechniqueCategory |
P3047
|
FINISHED |
| Object | rides and breakdowns |
—
|
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: rides and breakdowns | Statement: [Catch wrestling, hasNotableTechniqueCategory, rides and breakdowns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableTechniqueCategory Context triple: [Catch wrestling, hasNotableTechniqueCategory, rides and breakdowns]
-
A.
hasTechnique
chosen
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
B.
allowedTechnique
Indicates that a particular technique or method is permitted or acceptable to use in a given context or under specified rules.
-
C.
hasNotableFeature
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
-
D.
hasEponymousSkill
Indicates that an entity possesses a skill that is named after a particular person or entity.
-
E.
usedByTechnique
Indicates that a particular technique makes use of or employs the referenced entity as part of its method or 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_69c6996180088190832e38e8d83ff54a |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c705257ca08190a78c592a1e616da8 |
completed | March 27, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69c7016df2b08190b2330a2010691431 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:08 p.m.