Triple
T1844842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgin Orbit |
E41260
|
entity |
| Predicate | assetDisposition |
P34100
|
FINISHED |
| Object | assets sold at auction in 2023 |
—
|
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: assets sold at auction in 2023 | Statement: [Virgin Orbit, assetDisposition, assets sold at auction in 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assetDisposition Context triple: [Virgin Orbit, assetDisposition, assets sold at auction in 2023]
-
A.
assetType
Indicates the specific category or classification of an asset within a broader asset framework or system.
-
B.
notableAsset
Indicates that an entity possesses or is associated with an asset that is particularly significant, prominent, or noteworthy in relation to it.
-
C.
ownsAssetType
Indicates that an entity possesses ownership rights over an asset of a specified type.
-
D.
ownershipHistory
Indicates the sequence of past and present owners associated with an entity over time.
-
E.
ownedProperty
Indicates that one entity possesses legal ownership or control over another entity as property.
- F. None of above. chosen
Provenance (4 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdb0d2c8190a67f584e67979fa3 |
completed | March 7, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69abb32a8d548190a231c7c2ce276a5e |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:33 p.m.