Triple
T6874378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyalu B5 |
E158635
|
entity |
| Predicate | freeFrom |
P73865
|
FINISHED |
| Object | parabens (varies by product and market) |
—
|
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: parabens (varies by product and market) | Statement: [Hyalu B5, freeFrom, parabens (varies by product and market)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freeFrom Context triple: [Hyalu B5, freeFrom, parabens (varies by product and market)]
-
A.
freedBy
Indicates that an entity is released or liberated as a result of an action performed by another entity.
-
B.
freeSection
Indicates that a section or segment is available without cost or restrictions to the user.
-
C.
leasedFrom
Indicates that one entity is renting or leasing something from another entity, which acts as the owner or lessor.
-
D.
releaseForm
Indicates that one entity formally authorizes the release or disclosure of information, rights, or responsibilities to another entity through a consent or waiver document.
-
E.
releasedFor
Indicates that something has been made available or authorized for public use, distribution, or access.
- 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_69c68832af1481908ce356e133ebaebe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d8c8d3888190b1c1f74aa66d6071 |
completed | March 27, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b363dc8190a7225b540ab2bc40 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:22 p.m.