Triple
T2874193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hartford |
E56836
|
entity |
| Predicate | notableClientSegment |
P16877
|
FINISHED |
| Object | members of AARP |
—
|
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: members of AARP | Statement: [The Hartford, notableClientSegment, members of AARP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableClientSegment Context triple: [The Hartford, notableClientSegment, members of AARP]
-
A.
notableClient
Indicates that one entity serves as a prominent or distinguished client of another entity.
-
B.
notableSegmentType
Indicates that a particular segment or portion of something is classified as being of notable or special significance by its type.
-
C.
notableEngagement
Indicates a significant interaction, involvement, or participation between entities that is noteworthy or distinguished in some context.
-
D.
brandSegment
chosen
Indicates the specific market segment or customer group that a brand is targeted toward or associated with.
-
E.
hasNotableSegment
Indicates that an entity includes or contains a specific segment, part, or portion that is considered notable or significant in some way.
- 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe0032ddc8190bb4d15ec7e3c63e8 |
completed | March 7, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.