Triple
T7946306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tai Chi |
E184505
|
entity |
| Predicate | healthBenefitClaim |
P2188
|
FINISHED |
| Object | improved balance |
—
|
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: improved balance | Statement: [Tai Chi, healthBenefitClaim, improved balance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healthBenefitClaim Context triple: [Tai Chi, healthBenefitClaim, improved balance]
-
A.
benefitAdministered
Indicates that a benefit (such as aid, service, or entitlement) has been formally provided or delivered to an eligible recipient by an administering party.
-
B.
benefitProtection
Indicates that one entity provides protective advantages or safeguards that benefit another entity.
-
C.
CanadaClaimsAs
Indicates that Canada asserts ownership, sovereignty, or jurisdiction over the referenced entity or territory.
-
D.
claimProcess
Indicates the process by which a claim (such as an insurance or service claim) is received, evaluated, and resolved between involved parties.
-
E.
hasBenefit
chosen
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b29a570819091a2ac185a8d57c4 |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:09 p.m.