Triple
T15905259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revolver Entertainment |
E385695
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | independent company |
C17225
|
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: independent company Context triple: [Revolver Entertainment, instanceOf, independent company]
-
A.
independent organization
chosen
An independent organization is an entity that operates autonomously from external control or affiliation, making its own decisions, policies, and governance.
-
B.
company
A company is an organized entity, legally recognized or informally structured, that coordinates people and resources to produce goods or services for customers, typically in pursuit of profit or specific objectives.
-
C.
Alaska Native regional corporation
An Alaska Native regional corporation is a for-profit entity established under the Alaska Native Claims Settlement Act to manage land, financial assets, and business interests on behalf of Alaska Native shareholders within a specific geographic region.
-
D.
tribally owned holding company
A tribally owned holding company is a business entity owned and controlled by a Native American tribe or tribal government that manages and oversees a portfolio of subsidiary enterprises to generate revenue, support economic development, and advance tribal sovereignty and community goals.
-
E.
independent component city
An independent component city is a self-governing urban entity that operates administratively separate from surrounding regional or county structures, managing its own local affairs and services.
- F. None of above.
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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:52 a.m.