Triple
T18335399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Men’s Bodybuilding |
E439257
|
entity |
| Predicate | includesPoses |
P15582
|
FINISHED |
| Object | front double biceps |
—
|
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: front double biceps | Statement: [Open Men’s Bodybuilding, includesPoses, front double biceps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPoses Context triple: [Open Men’s Bodybuilding, includesPoses, front double biceps]
-
A.
showsPose
chosen
Indicates that one entity displays or presents a particular pose or bodily posture of another entity.
-
B.
initiallyPosesAs
Indicates that one entity first presents itself under a false or alternative identity or role to another entity before its true nature or role is revealed.
-
C.
typicalPositionsInclude
Indicates that certain positions or roles are commonly or characteristically included within something (such as an organization, structure, or context).
-
D.
hasPositionsFor
Indicates that one entity offers or contains available roles, jobs, or positions for another entity.
-
E.
positions
Indicates that one entity assigns, arranges, or places another entity in a specific location, role, or order relative to others.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50ecd759481909703ed2d0d68199f |
completed | April 19, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.