Triple
T27086802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lancashire wrestling |
E686056
|
entity |
| Predicate | gripRule |
P161836
|
FINISHED |
| Object | no fixed starting hold |
—
|
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: no fixed starting hold | Statement: [Lancashire wrestling, gripRule, no fixed starting hold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gripRule Context triple: [Lancashire wrestling, gripRule, no fixed starting hold]
-
A.
groupingRule
Indicates a rule or criterion that defines how multiple entities are grouped or clustered together based on shared characteristics or conditions.
-
B.
styleOfRule
Indicates the stylistic or formatting convention that a particular rule follows or is expressed in.
-
C.
underRule
Indicates that one entity is governed, controlled, or subject to the authority, rules, or dominion of another entity.
-
D.
isRuleGoverned
Indicates that an entity’s behavior, structure, or operation is determined and constrained by explicit rules or formal regulations.
-
E.
strictRule
Indicates that a rule is enforced rigidly, allowing no exceptions, flexibility, or deviation in its application.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f61fa35ac48190890102c348ed81a0 |
completed | May 2, 2026, 4 p.m. |
Created at: April 27, 2026, 8:38 a.m.