Triple
T22239563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nemax 50 |
E549683
|
entity |
| Predicate | marketSegmentType |
P146868
|
FINISHED |
| Object | growth segment |
—
|
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: growth segment | Statement: [Nemax 50, marketSegmentType, growth segment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketSegmentType Context triple: [Nemax 50, marketSegmentType, growth segment]
-
A.
marketSegmentPreviewed
Indicates that a specific market segment has been reviewed or examined in advance, typically as part of planning, analysis, or evaluation activities.
-
B.
marketSegmentCoverage
Indicates the extent to which a product, service, or campaign reaches or serves the intended market segment(s).
-
C.
brandSegment
Indicates the specific market segment or customer group that a brand is targeted toward or associated with.
-
D.
governsMarketSegment
Indicates that an entity has controlling influence or regulatory authority over a particular market segment.
-
E.
hasMarketSegmentFor
Indicates that an entity targets or serves a specific market segment for its products or services.
- F. None of above. chosen
Provenance (4 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f132133b908190b0fb32a5ee68e1e6 |
completed | April 28, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
| PDg | Predicate description generation | batch_69e7222e74248190a2d3671049f117f2 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:38 p.m.