Triple
T35806394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock Bottom |
E1035110
|
entity |
| Predicate | requiresStrength |
P200925
|
FINISHED |
| Object | upper body strength |
—
|
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: upper body strength | Statement: [Rock Bottom, requiresStrength, upper body strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresStrength Context triple: [Rock Bottom, requiresStrength, upper body strength]
-
A.
requiresPass
Indicates that access to or participation in something is conditional on possessing a valid pass.
-
B.
estimatedStrength
Indicates that a value represents an approximate or inferred level, magnitude, or intensity of something rather than a precisely measured strength.
-
C.
availableStrength
Indicates the amount of strength or power that an entity currently has ready for use or deployment.
-
D.
initialAuthorizedStrength
Indicates the originally approved or designated level, size, or capacity of a force, group, or resource at the time it was first authorized.
-
E.
enforcementStrength
Indicates the degree or intensity with which rules, laws, or policies are applied and enforced in a given context.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69ffb97ae1508190bf3addd6e2aac281 |
completed | May 9, 2026, 10:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.