Triple
T13976594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travelers Group |
E336201
|
entity |
| Predicate | hadBusinessSegment |
P7588
|
FINISHED |
| Object | consumer finance |
—
|
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: consumer finance | Statement: [Travelers Group, hadBusinessSegment, consumer finance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadBusinessSegment Context triple: [Travelers Group, hadBusinessSegment, consumer finance]
-
A.
hasBusiness
Indicates that one entity owns, operates, or is formally associated with a business entity.
-
B.
hasBusinessTypeAlong
Indicates that a business or commercial entity located along a route, corridor, or area is associated with a specific type or category of business activity.
-
C.
hasBusinessDivision
chosen
Indicates that an organization includes or is composed of a specific business division as a subordinate unit.
-
D.
hasBusinessNode
Indicates that an entity is associated with, linked to, or represented by a specific business-related node within a business structure or network.
-
E.
hasBusinesses
Indicates that an entity owns, operates, or is associated with one or more businesses.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e90dc148190b38e339aac0de484 |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.