Triple
T36842351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Crew |
E910440
|
entity |
| Predicate | typicalEndUser |
P160218
|
FINISHED |
| Object | men seeking professional grooming products |
—
|
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: men seeking professional grooming products | Statement: [American Crew, typicalEndUser, men seeking professional grooming products]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEndUser Context triple: [American Crew, typicalEndUser, men seeking professional grooming products]
-
A.
endUser
chosen
Indicates that an entity is the final consumer or recipient of a product, service, or action in the relationship.
-
B.
traditionalUser
Indicates that a user engages with or is characterized by conventional, established, or customary practices, behaviors, or methods.
-
C.
user
Indicates a relationship where an entity actively operates, controls, or interacts with another entity, typically as the primary agent or consumer of its function.
-
D.
typicalProfile
Indicates that an entity represents the standard or most representative profile or pattern for another entity.
-
E.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.