Triple
T78183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weyerhaeuser Company |
E1563
|
entity |
| Predicate | hasCustomerType |
P809
|
FINISHED |
| Object | construction 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: construction industry | Statement: [Weyerhaeuser Company, hasCustomerType, construction industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomerType Context triple: [Weyerhaeuser Company, hasCustomerType, construction industry]
-
A.
customerType
chosen
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
-
B.
hasVisitorType
Indicates the type or category of visitor associated with an entity (e.g., guest, customer, tourist, patient).
-
C.
hasMemberType
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
D.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
E.
hasCommunityType
Indicates that an entity is associated with or classified under a particular type or category of community.
- 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_69a24c60d19c8190a1b6c105ca59ef5b |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a2559892dc81909303f2eefdc0025f |
completed | Feb. 28, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69a24eaf99e481908e8d314577e22ecf |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.