Triple
T27086776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lancashire wrestling |
E686056
|
entity |
| Predicate | styleOfWrestling |
P92886
|
FINISHED |
| Object | catch-as-catch-can |
—
|
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: catch-as-catch-can | Statement: [Lancashire wrestling, styleOfWrestling, catch-as-catch-can]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleOfWrestling Context triple: [Lancashire wrestling, styleOfWrestling, catch-as-catch-can]
-
A.
typeOfWrestling
chosen
Indicates the specific style or category of wrestling that characterizes a given wrestling activity or event.
-
B.
wrestlingRole
Indicates the specific capacity or function an individual performs within a wrestling context, such as competitor, referee, coach, or other defined role.
-
C.
boxingStyleCharacteristic
Indicates that a particular boxing style possesses or is defined by a specific characteristic or attribute.
-
D.
wrestledWith
Indicates that one entity engaged in a physical wrestling contest or struggle with another entity.
-
E.
wrestlingTradition
Indicates a cultural or historical practice of wrestling that is characteristic of or maintained by an entity.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62346348081909de57928856e2c8b |
completed | May 2, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:38 a.m.