Triple
T6737885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LS |
E154001
|
entity |
| Predicate | typicalBuyerSegment |
P16877
|
FINISHED |
| Object | price-sensitive buyers |
—
|
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: price-sensitive buyers | Statement: [LS, typicalBuyerSegment, price-sensitive buyers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBuyerSegment Context triple: [LS, typicalBuyerSegment, price-sensitive buyers]
-
A.
typicalProfile
Indicates that an entity represents the standard or most representative profile or pattern for another entity.
-
B.
typicalAudience
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
C.
brandSegment
chosen
Indicates the specific market segment or customer group that a brand is targeted toward or associated with.
-
D.
typicalGroup
Indicates that the subject belongs to or represents a standard, characteristic, or commonly occurring group associated with the object.
-
E.
typicalSegmentType
Indicates that something is classified as belonging to a usual or characteristic type of segment within a broader structure or sequence.
- 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_69c6880d84d8819095d19de2295f26ac |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1850a288190aa7e647fefbb0ede |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d09067a0819087ed6c820f4699f8 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:10 p.m.