Triple
T2927571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GEHA |
E78882
|
entity |
| Predicate | targetCustomerType |
P481
|
FINISHED |
| Object | public sector employees |
—
|
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: public sector employees | Statement: [GEHA, targetCustomerType, public sector employees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetCustomerType Context triple: [GEHA, targetCustomerType, public sector employees]
-
A.
customerType
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
-
B.
targetMarket
chosen
Indicates the group of consumers or organizations that a product, service, or campaign is specifically intended and designed to reach.
-
C.
primaryTargetType
Indicates the main category or type of entity that is the principal focus or intended recipient of an action, effect, or operation.
-
D.
majorCustomer
Indicates that one entity is a primary or high-value customer of another entity, typically contributing a significant portion of business or revenue.
-
E.
targetsGroup
Indicates that an action, influence, or effect is directed toward a specific group as its intended recipient or focus.
- 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9606e8348190bb19df33a2709674 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:55 p.m.