Triple
T18419067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Men’s Physique Olympia |
E441972
|
entity |
| Predicate | poses |
P91860
|
FINISHED |
| Object | front stance |
—
|
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 stance | Statement: [Men’s Physique Olympia, poses, front stance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: poses Context triple: [Men’s Physique Olympia, poses, front stance]
-
A.
positions
Indicates that one entity assigns, arranges, or places another entity in a specific location, role, or order relative to others.
-
B.
posedIn
chosen
Indicates that an entity assumed a particular physical position or posture, typically for the purpose of being observed, photographed, drawn, or otherwise depicted.
-
C.
resents
Indicates that one entity feels bitterness, anger, or lingering ill will toward another, typically due to a perceived wrong or unfair treatment.
-
D.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
E.
par
Indicates that two entities are parallel to each other in space or direction.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51a2a0fb08190b409ed200a9d86a6 |
completed | April 19, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 10:47 a.m.