Triple
T28902460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blade Runner Partnership |
E732984
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special-purpose production entity |
C55391
|
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: special-purpose production entity Context triple: [Blade Runner Partnership, instanceOf, special-purpose production entity]
-
A.
special purpose entity
A special purpose entity is a legally separate organization created by a parent company to isolate financial risk, hold specific assets or liabilities, or conduct narrowly defined activities, often for financing or regulatory purposes.
-
B.
special-purpose vehicle
A special-purpose vehicle is a legally separate entity created by a parent organization to isolate financial risk and carry out a specific, narrowly defined set of activities or transactions.
-
C.
specialized institution
A specialized institution is an organization dedicated to a specific field or function, providing focused services, expertise, or education within that domain.
-
D.
special-purpose governmental unit
A special-purpose governmental unit is a limited-scope public entity, such as a school district or water authority, created by law to perform a specific governmental function or set of functions within a defined geographic area.
-
E.
special-purpose vessel
A special-purpose vessel is a ship specifically designed and equipped to perform dedicated tasks or services that cannot be efficiently carried out by standard commercial or passenger vessels.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 8:04 a.m.