Triple
T33701539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gerald Croft |
E863466
|
entity |
| Predicate | businessConnection |
P177213
|
FINISHED |
| Object | Crofts Limited |
—
|
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: Crofts Limited | Statement: [Gerald Croft, businessConnection, Crofts Limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: businessConnection Context triple: [Gerald Croft, businessConnection, Crofts Limited]
-
A.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another entity.
-
B.
businessEntity
Indicates a relationship where an entity functions as or is classified as a business or commercial organization.
-
C.
businessVenture
Indicates a relationship where entities jointly engage in, operate, or are involved with a commercial or entrepreneurial undertaking.
-
D.
businessFunction
Indicates the specific role, activity, or operational function that an entity performs within a business context.
-
E.
businessForm
Indicates the legal or organizational structure under which a business operates (e.g., sole proprietorship, partnership, corporation).
- F. None of above. chosen
Provenance (4 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fae2a7a8819099945d1706a94bfd |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fa335b908190a20d92d5396203b5 |
completed | May 3, 2026, 7:33 a.m. |
Created at: May 1, 2026, 1:43 a.m.