Triple
T11943429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J. W. Steere & Son |
E284234
|
entity |
| Predicate | hasBusinessStructure |
P96805
|
FINISHED |
| Object | family business |
—
|
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: family business | Statement: [J. W. Steere & Son, hasBusinessStructure, family business]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusinessStructure Context triple: [J. W. Steere & Son, hasBusinessStructure, family business]
-
A.
hasBusiness
Indicates that one entity owns, operates, or is formally associated with a business entity.
-
B.
hasLegalStructure
chosen
Indicates that an entity possesses a specific formal legal organization or classification under law.
-
C.
hasTypeOfBusinesses
Indicates that an entity is associated with or contains specific categories or kinds of businesses.
-
D.
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.
-
E.
hasBusinessNode
Indicates that an entity is associated with, linked to, or represented by a specific business-related node within a business structure or network.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9034444488190925a6fa6c856ed08 |
completed | April 10, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.