Triple
T19691631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Healthy Request |
E472847
|
entity |
| Predicate | hasLabelClaimType |
P85731
|
FINISHED |
| Object | nutrition-focused labeling |
—
|
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: nutrition-focused labeling | Statement: [Healthy Request, hasLabelClaimType, nutrition-focused labeling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLabelClaimType Context triple: [Healthy Request, hasLabelClaimType, nutrition-focused labeling]
-
A.
hasClaimType
chosen
Indicates that an entity is associated with or categorized under a specific type of claim.
-
B.
hasLabel
Indicates that an entity is associated with a specific textual label or name used to identify or describe it.
-
C.
hasKeyClaim
Indicates that one entity contains, presents, or is associated with a central or primary claim expressed by another entity.
-
D.
attributeClaim
Indicates that one entity asserts or specifies a particular attribute or property about another entity.
-
E.
hasLabelSet
Indicates that an entity is associated with a specific collection or set of labels.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6421013c4819095e80aadfe590102 |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.