Triple
T38439620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frankie Bergstein |
E906450
|
entity |
| Predicate | formsBusinessWith |
P177213
|
FINISHED |
| Object | Grace Hanson |
—
|
NE NERFINISHED |
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: Grace Hanson | Statement: [Frankie Bergstein, formsBusinessWith, Grace Hanson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsBusinessWith Context triple: [Frankie Bergstein, formsBusinessWith, Grace Hanson]
-
A.
businessForm
Indicates the legal or organizational structure under which a business operates (e.g., sole proprietorship, partnership, corporation).
-
B.
businessConnection
chosen
Indicates a professional or commercial relationship exists between the entities, such as partnership, collaboration, or other business-related association.
-
C.
commercialForm
Indicates the commercial or marketed form in which something (such as a product, substance, or medicine) is offered or sold.
-
D.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another entity.
-
E.
businessFunction
Indicates the specific role, activity, or operational function that an entity performs within a business context.
- 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_69f76e72878c8190a692836c8b01b58b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: May 3, 2026, 4:31 p.m.