Triple
T14764396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google infrastructure |
E346956
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | proprietary technology stack |
C35110
|
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 technology stack Context triple: [Google infrastructure, instanceOf, proprietary technology stack]
-
A.
proprietary game engine
A proprietary game engine is a privately owned, closed-source software framework used by a specific company or developer to create, run, and optimize video games, typically not licensed for public modification or broad third-party use.
-
B.
proprietary codec
A proprietary codec is a closed, privately owned method for encoding and decoding digital data (such as audio or video) that typically requires licensing or permission to use.
-
C.
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.
-
D.
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.
-
E.
proprietary governor
A proprietary governor is a colonial-era official or authority figure granted governing powers over a territory by a private owner or chartered company rather than directly by a sovereign state.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:30 a.m.