Triple
T18335380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Men’s Bodybuilding |
E439257
|
entity |
| Predicate | hasParticipantAttribute |
P131408
|
FINISHED |
| Object | high muscle mass |
—
|
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: high muscle mass | Statement: [Open Men’s Bodybuilding, hasParticipantAttribute, high muscle mass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParticipantAttribute Context triple: [Open Men’s Bodybuilding, hasParticipantAttribute, high muscle mass]
-
A.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
B.
hasParticipantForce
Indicates that an event or action involves a participant specifically in the role of exerting or applying force.
-
C.
hasFormerParticipant
Indicates that an entity once participated in an activity, event, or organization but is no longer a current participant.
-
D.
hasGlobalParticipation
Indicates that an entity is involved in or contributes to activities, initiatives, or operations that span multiple countries or have worldwide scope.
-
E.
hasCommunityAttribute
Indicates that a community possesses or is characterized by a specific attribute or property.
- 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_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. |
| PDg | Predicate description generation | batch_69e4561d665081908ec555344e76d82b |
completed | April 19, 2026, 4:12 a.m. |
Created at: April 10, 2026, 10:36 a.m.