Triple
T18335718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wellness Olympia |
E439264
|
entity |
| Predicate | emphasisComparedToFigure |
P103469
|
FINISHED |
| Object | less upper-body muscularity |
—
|
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: less upper-body muscularity | Statement: [Wellness Olympia, emphasisComparedToFigure, less upper-body muscularity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasisComparedToFigure Context triple: [Wellness Olympia, emphasisComparedToFigure, less upper-body muscularity]
-
A.
hasEmphasis
Indicates that one element is given special stress, importance, or prominence relative to others.
-
B.
positionEmphasized
Indicates that a particular position, stance, or role is given special prominence or stress relative to others.
-
C.
hasRelativeProminenceComparedTo
chosen
Indicates that one entity has a greater, lesser, or otherwise specified level of prominence or importance when compared to another entity.
-
D.
visualImportance
Indicates how visually prominent or attention‑drawing one entity is relative to others in a given context.
-
E.
contrastUse
Indicates that one entity is used in opposition or distinction to another to highlight differences between them.
- 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:37 a.m.