Triple
T38114166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croslite foam resin |
E951745
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | proprietary material |
C66445
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: proprietary material Context triple: [Croslite foam resin, instanceOf, proprietary material]
-
A.
proprietary license
A proprietary license is a legal agreement that grants users limited rights to use, but not freely modify or redistribute, software or other intellectual property owned and controlled by a specific individual or organization.
-
B.
proprietary language
A proprietary language is a programming or specification language owned and controlled by an individual or organization, with usage, modification, and distribution restricted by licenses or other legal protections.
-
C.
proprietary government
A proprietary government is a form of governance in which a territory is owned and ruled as the private property of an individual or group, who exercise political authority much like a landlord over an estate.
-
D.
reserved matter
A reserved matter is a specific decision or issue that, under a constitution, statute, or corporate governance framework, is kept under the exclusive authority of a higher-level body (such as a central government, shareholders, or a board) and cannot be decided by subordinate entities without its consent.
-
E.
proprietary file format
A proprietary file format is a data storage structure whose specifications are owned and controlled by an individual or organization, often restricting interoperability and requiring specific software to access or modify its contents.
- F. None of above. chosen
Provenance (1 batch)
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_69f76f07734c8190814e937e12257a78 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.