Triple
T32956453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Lumber Company (West + fir) |
E843113
|
entity |
| Predicate | hadCompanyTown |
P22798
|
FINISHED |
| Object | Westfir |
—
|
NE NERFINISHED |
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: Westfir | Statement: [Western Lumber Company (West + fir), hadCompanyTown, Westfir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadCompanyTown Context triple: [Western Lumber Company (West + fir), hadCompanyTown, Westfir]
-
A.
hadCompanyAt
Indicates that an entity was accompanied by or in the presence of another entity at a specific time or place.
-
B.
hasTown
Indicates that one entity possesses, contains, or is associated with a town as part of its structure, jurisdiction, or composition.
-
C.
hadCity
Indicates that an entity was formerly associated with or located in a particular city.
-
D.
isCompanyTownFor
chosen
Indicates that one location functions as a company town whose economy, services, or governance are predominantly controlled or dominated by a specific company.
-
E.
hadMajorCompany
Indicates that an entity previously owned, led, or was primarily associated with a major company.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d175fc988190ad4872c9b647b71d |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.