Triple
T34956189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cream |
E1008127
|
entity |
| Predicate | targetsUserType |
P55187
|
FINISHED |
| Object | beginners |
—
|
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: beginners | Statement: [Cream, targetsUserType, beginners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsUserType Context triple: [Cream, targetsUserType, beginners]
-
A.
targetRole
Indicates the specific role or function that an entity is intended or designated to fulfill in a given context.
-
B.
supportsUserType
chosen
Indicates that one entity is compatible with, or provides functionality for, a specified type or category of user.
-
C.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with another entity.
-
D.
speciesOfPrimaryUser
Indicates the biological species to which the primary user of something (e.g., a device, service, or resource) belongs.
-
E.
typicalTargetType
Indicates the usual or most common type or category of entity that serves as the target or recipient in a given relationship or action.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
Created at: May 3, 2026, 4 p.m.