Triple
T27879566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockdown |
E705049
|
entity |
| Predicate | hasNotableMatch |
P184318
|
FINISHED |
| Object | Lethal Lockdown match |
—
|
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: Lethal Lockdown match | Statement: [Lockdown, hasNotableMatch, Lethal Lockdown match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableMatch Context triple: [Lockdown, hasNotableMatch, Lethal Lockdown match]
-
A.
hadNotableMatch
chosen
Indicates that an entity participated in a specific match or contest that is considered significant or noteworthy.
-
B.
notableMatch
Indicates that there exists a particularly significant or noteworthy match or pairing between the related entities.
-
C.
hasNotableScore
Indicates that an entity is associated with a score or rating considered significant or noteworthy in its context.
-
D.
hasNotableContender
Indicates that an entity has a significant rival, challenger, or competitor recognized as noteworthy in relation to it.
-
E.
hasNotableHit
Indicates that an entity is associated with a particularly successful, famous, or widely recognized work, performance, or achievement.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fedd5a5f4c8190acce88db56303703 |
completed | May 9, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69fed910b31c8190ae837163d146738d |
completed | May 9, 2026, 6:49 a.m. |
Created at: April 27, 2026, 6:29 p.m.