Triple
T32527596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salt |
E831356
|
entity |
| Predicate | excessIntakeAssociatedWith |
P174553
|
FINISHED |
| Object | hypertension |
—
|
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: hypertension | Statement: [Salt, excessIntakeAssociatedWith, hypertension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excessIntakeAssociatedWith Context triple: [Salt, excessIntakeAssociatedWith, hypertension]
-
A.
intendedIntake
Indicates the amount or type of something (such as a substance, nutrient, or resource) that is planned or prescribed to be taken in by an entity.
-
B.
intendedConsumption
Indicates that one entity is meant or designed to be consumed or used up by another entity.
-
C.
intake
Indicates the act of taking something in or consuming it, such as food, drink, or other substances, into a system or organism.
-
D.
overactivityAssociatedWith
Indicates that a state of excessive activity is linked or correlated with another condition, factor, or outcome.
-
E.
largelyConsumedBy
Indicates that something is mostly or predominantly eaten or used up by a particular consumer or group.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c519b0ec81909f4077ceb59e0f88 |
completed | May 3, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1:01 a.m.