Triple
T30511298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norah Lorkowski |
E776431
|
entity |
| Predicate | joinsBusinessWith |
P150695
|
FINISHED |
| Object | Rose Lorkowski |
—
|
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: Rose Lorkowski | Statement: [Norah Lorkowski, joinsBusinessWith, Rose Lorkowski]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinsBusinessWith Context triple: [Norah Lorkowski, joinsBusinessWith, Rose Lorkowski]
-
A.
joins
Indicates that one entity becomes a member or part of another entity, typically by entering into an organization, group, or association.
-
B.
hasBusinessIn
Indicates that one entity conducts, operates, or maintains business activities within the jurisdiction, location, or domain of another entity.
-
C.
hasJointVenture
Indicates that two or more entities are engaged together in a formally established joint business venture or collaborative commercial undertaking.
-
D.
coRunsBusinessWith
chosen
Indicates that two or more entities jointly operate or manage a business together as partners or collaborators.
-
E.
hasBusiness
Indicates that one entity owns, operates, or is formally associated with a business entity.
- 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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f687b9ebc881909b90ddefcf0668ed |
completed | May 2, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:16 p.m.