Triple
T21976935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daniel Bryan |
E542728
|
entity |
| Predicate | signatureMove |
P15416
|
FINISHED |
| Object |
Yes Lock
The Yes Lock is a professional wrestling submission hold popularized by Daniel Bryan, combining a crossface and arm trap to force opponents to tap out.
|
E1511480
|
NE FINISHED |
How this triple was built (4 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: Yes Lock | Statement: [Daniel Bryan, signatureMove, Yes Lock]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yes Lock Context triple: [Daniel Bryan, signatureMove, Yes Lock]
-
A.
Lock 45
Lock 45 is the final lock on Ontario’s Trent–Severn Waterway, located at Port Severn where the canal meets Georgian Bay.
-
B.
Ware Lock
Ware Lock is a canal lock on the River Lee Navigation in Hertfordshire, England, used to raise and lower boats between different water levels.
-
C.
Lock 43
Lock 43, also known as Swift Rapids Lock, is a large lock on Ontario’s Trent–Severn Waterway notable for its significant lift and remote, scenic location.
-
D.
Lock
Lock is a small rural town in South Australia’s Eyre Peninsula, known primarily for its grain farming and surrounding agricultural land.
-
E.
Lock
Lock is a Symfony component that provides a robust locking mechanism to prevent concurrent access conflicts in shared resources.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Yes Lock Triple: [Daniel Bryan, signatureMove, Yes Lock]
Generated description
The Yes Lock is a professional wrestling submission hold popularized by Daniel Bryan, combining a crossface and arm trap to force opponents to tap out.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Yes Lock Target entity description: The Yes Lock is a professional wrestling submission hold popularized by Daniel Bryan, combining a crossface and arm trap to force opponents to tap out.
-
A.
Lock 45
Lock 45 is the final lock on Ontario’s Trent–Severn Waterway, located at Port Severn where the canal meets Georgian Bay.
-
B.
Ware Lock
Ware Lock is a canal lock on the River Lee Navigation in Hertfordshire, England, used to raise and lower boats between different water levels.
-
C.
Lock 43
Lock 43, also known as Swift Rapids Lock, is a large lock on Ontario’s Trent–Severn Waterway notable for its significant lift and remote, scenic location.
-
D.
Lock
Lock is a Symfony component that provides a robust locking mechanism to prevent concurrent access conflicts in shared resources.
-
E.
Lock
Lock is a small rural town in South Australia’s Eyre Peninsula, known primarily for its grain farming and surrounding agricultural land.
- F. None of above. chosen
Provenance (5 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_69e0c48070988190909db97667b9a0ac |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12489889c81909c847cf2f6808d85 |
completed | April 28, 2026, 9:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0a6d731c64819099fd3188eda0a5bf |
completed | May 18, 2026, 1:37 a.m. |
| NEDg | Description generation | batch_6a0a6e05677c819082f0613fbf6aeff0 |
completed | May 18, 2026, 1:40 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0a6e93dfe88190bcddd1802017ddea |
completed | May 18, 2026, 1:42 a.m. |
Created at: April 16, 2026, 8:03 p.m.