Triple
T2650320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pella Impervia |
E53881
|
entity |
| Predicate | offeredWith |
P13910
|
FINISHED |
| Object | various interior color finishes |
—
|
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: various interior color finishes | Statement: [Pella Impervia, offeredWith, various interior color finishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredWith Context triple: [Pella Impervia, offeredWith, various interior color finishes]
-
A.
offeredIn
Indicates that something is made available or provided within a particular context, setting, or medium.
-
B.
offering
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
-
C.
offeringType
Indicates the category or nature of what is being offered in a transaction or interaction (e.g., product, service, or other type of offering).
-
D.
availableWith
chosen
Indicates that one entity can be obtained, accessed, or used in conjunction with another entity.
-
E.
associatedOffering
Indicates a relationship where one offering is linked or connected to another offering as related or contextually relevant.
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd92f5f508190b4ca396c3f399e93 |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd814298c8190952f05aed43f6bb8 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.