Triple
T31623669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paterson Great Falls |
E806961
|
entity |
| Predicate | industrialUses |
P8461
|
FINISHED |
| Object | textile mills |
—
|
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 mills | Statement: [Paterson Great Falls, industrialUses, textile mills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industrialUses Context triple: [Paterson Great Falls, industrialUses, textile mills]
-
A.
postIndustrialUse
Indicates how something is utilized or purposed after its original industrial function or phase has ended.
-
B.
usedInIndustry
chosen
Indicates that something is employed or applied within a particular industry or industrial sector.
-
C.
industrialCategory
Indicates the industry or sector classification to which an entity (such as a business or organization) belongs.
-
D.
industrialUseEnd
Indicates the point in time or condition at which an industrial use or application of something is terminated or ceases.
-
E.
hasIndustrialSignificance
Indicates that something plays an important role or has notable impact within industrial processes, production, or applications.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8afff6481909ece081c67160a08 |
completed | May 3, 2026, 1:45 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:42 p.m.