Triple
T23853887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max Blanck |
E592248
|
entity |
| Predicate | typeOfBusinessOwned |
P68868
|
FINISHED |
| Object | shirtwaist factory |
—
|
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: shirtwaist factory | Statement: [Max Blanck, typeOfBusinessOwned, shirtwaist factory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBusinessOwned Context triple: [Max Blanck, typeOfBusinessOwned, shirtwaist factory]
-
A.
typeOfBusinessOrganization
Indicates the specific kind or category of business organization that an entity belongs to (e.g., corporation, partnership, sole proprietorship).
-
B.
hasTypeOfBusinesses
chosen
Indicates that an entity is associated with or contains specific categories or kinds of businesses.
-
C.
stateOfBusiness
Indicates the current operational or financial condition or status of a business at a given point in time.
-
D.
eligibleBusinessType
Indicates that a business entity qualifies under specified criteria to be considered an eligible type for a particular program, rule, or context.
-
E.
typeOfBusinessItSchedules
Indicates that an entity is responsible for scheduling activities or operations for a particular type of business.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c98954748190b39e0ac69e5625f9 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:11 p.m.