Triple
T21371660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lumberport, West Virginia |
E527078
|
entity |
| Predicate | historicallyTiedToIndustry |
P3008
|
FINISHED |
| Object | lumber 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: lumber industry | Statement: [Lumberport, West Virginia, historicallyTiedToIndustry, lumber industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyTiedToIndustry Context triple: [Lumberport, West Virginia, historicallyTiedToIndustry, lumber industry]
-
A.
hasHistoricIndustry
chosen
Indicates that an entity has been associated with a notable or historically significant industry or industrial activity in the past.
-
B.
foundingIndustry
Indicates the industry or sector in which an entity was originally founded or began its primary operations.
-
C.
formerKeyIndustry
Indicates that an entity was once a primary or strategically important industry for another entity but no longer holds that status.
-
D.
hadStateOwnershipOfIndustry
Indicates that a governing authority or state entity possessed ownership and control over a particular industry.
-
E.
historicallyLinked
Indicates that two entities are connected through a shared or related historical event, period, or development.
- 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_69e0b51e80808190ba5cb05667af02a9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0af44d88190aedd3b2127bb297d |
completed | April 22, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:10 p.m.