Triple
T7509451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Crowthers of Bankdam |
E177479
|
entity |
| Predicate | centralBusiness |
P77383
|
FINISHED |
| Object | textile mill |
—
|
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: textile mill | Statement: [The Crowthers of Bankdam, centralBusiness, textile mill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralBusiness Context triple: [The Crowthers of Bankdam, centralBusiness, textile mill]
-
A.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another entity.
-
B.
commercialArea
Indicates that the location or region is designated primarily for commercial activities such as businesses, shops, or services.
-
C.
commercial
Indicates that one entity is engaged in a business-related or profit-oriented relationship, activity, or transaction with another entity.
-
D.
businessFunction
Indicates the specific role, activity, or operational function that an entity performs within a business context.
-
E.
business
Indicates that an entity is engaged in commercial or professional activities, such as providing goods or services for profit.
- 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_69c69f276b108190af2cc790b6554544 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5d052888190ae8678f9134d737c |
completed | March 27, 2026, 9:25 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d44e9481909813e073b194f6f4 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f574d8a8819095749518dad13791 |
completed | March 27, 2026, 9:24 p.m. |
Created at: March 27, 2026, 3:45 p.m.