Triple
T1292579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Active Cosmetics Division |
E27578
|
entity |
| Predicate | targetCondition |
P860
|
FINISHED |
| Object | acne-prone skin |
—
|
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: acne-prone skin | Statement: [Active Cosmetics Division, targetCondition, acne-prone skin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetCondition Context triple: [Active Cosmetics Division, targetCondition, acne-prone skin]
-
A.
coreCondition
Indicates that something serves as the primary or fundamental condition that must hold for a situation, process, or relationship to apply.
-
B.
target
chosen
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
C.
presentCondition
Indicates that an entity currently has or exhibits a particular state, situation, or condition.
-
D.
authorizationCondition
Indicates the specific rules or requirements that must be satisfied for an action or access to be legally or formally authorized.
-
E.
navigationCondition
Indicates the specific circumstances or requirements that must be satisfied for a navigation action or route to be valid or taken.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c3bb3a9c81909db2ad91defd87b6 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bee64d908190b6a9bb479959d523 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.