Triple
T16669478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rumford Branch |
E405070
|
entity |
| Predicate | connectsToIndustry |
P47404
|
FINISHED |
| Object | paper 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: paper mills | Statement: [Rumford Branch, connectsToIndustry, paper mills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToIndustry Context triple: [Rumford Branch, connectsToIndustry, paper mills]
-
A.
industryConnection
Indicates a professional or business relationship linking entities within the same or related industries, such as partnerships, collaborations, or shared sector involvement.
-
B.
relationToIndustry
chosen
Indicates how an entity is connected or relevant to a particular industry, such as through involvement, impact, or association.
-
C.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
D.
supportedIndustry
Indicates that one entity provides backing, resources, or services to help sustain or advance a particular industry.
-
E.
industryExposure
Indicates the extent to which an entity is involved in, affected by, or financially linked to a particular industry or set of industries.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37c9fa3d081909457b1bdea1d96e0 |
completed | April 18, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.