Triple
T20071207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rivelin Corn Mill (site) |
E499740
|
entity |
| Predicate | hasIndustrialCategory |
P53889
|
FINISHED |
| Object | water-powered industry |
—
|
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: water-powered industry | Statement: [Rivelin Corn Mill (site), hasIndustrialCategory, water-powered industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndustrialCategory Context triple: [Rivelin Corn Mill (site), hasIndustrialCategory, water-powered industry]
-
A.
hasIndustrialSector
Indicates that an entity is associated with, operates in, or belongs to a particular industrial sector or branch of economic activity.
-
B.
industrialCategory
chosen
Indicates the industry or sector classification to which an entity (such as a business or organization) belongs.
-
C.
hasIndustrialCompany
Indicates that one entity possesses, controls, or is associated with an industrial company.
-
D.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
E.
hasIndustrialAreaType
Indicates that an entity’s industrial area is classified as a specific type or category of industrial zone.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66438633481908710907c48806499 |
completed | April 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:40 p.m.