Triple
T5700015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boulton and Watt |
E125634
|
entity |
| Predicate | mainBusinessActivity |
P40655
|
FINISHED |
| Object | design of steam engines |
—
|
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: design of steam engines | Statement: [Boulton and Watt, mainBusinessActivity, design of steam engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainBusinessActivity Context triple: [Boulton and Watt, mainBusinessActivity, design of steam engines]
-
A.
commercialActivity
Indicates an action or relationship involving the buying, selling, or exchange of goods or services for profit or other economic gain.
-
B.
placeOfBusinessActivity
Indicates the type or nature of business activity that is conducted at a particular place or location.
-
C.
majorActivity
chosen
Indicates that the related entity performs, participates in, or is primarily associated with a main or most significant activity.
-
D.
businessFunction
Indicates the specific role, activity, or operational function that an entity performs within a business context.
-
E.
laterMainBusiness
Indicates that one business activity or enterprise occurs after and succeeds another as the main 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_69c0082c96988190b3a6a201edce472a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0241030408190be774a5d2ca6e999 |
completed | March 22, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69c021c2d8bc8190b947c7d1f423d2f3 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:45 p.m.