Triple
T35330021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sport Clips |
E1020291
|
entity |
| Predicate | primaryCustomerNeed |
P125614
|
FINISHED |
| Object | convenient haircuts for men and boys |
—
|
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: convenient haircuts for men and boys | Statement: [Sport Clips, primaryCustomerNeed, convenient haircuts for men and boys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCustomerNeed Context triple: [Sport Clips, primaryCustomerNeed, convenient haircuts for men and boys]
-
A.
targetConsumerNeed
chosen
Indicates that something is intended to address, satisfy, or be directed toward a specific need or requirement of a consumer.
-
B.
primaryCustomersInUniverse
Indicates that certain customers are designated as the main or most significant customers within a defined overall customer set or universe.
-
C.
customerFocus
Indicates that one entity prioritizes understanding and meeting the needs, preferences, or satisfaction of another entity (typically a customer or client).
-
D.
primaryIntent
Indicates the main purpose, goal, or motivation underlying an action, event, or relationship among entities.
-
E.
primaryIssue
Indicates that the related item is the main or most important issue among a set of issues.
- 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.