Triple
T1844817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgin Orbit |
E41260
|
entity |
| Predicate | Dan HartRole |
P34096
|
FINISHED |
| Object | Chief Executive Officer |
—
|
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: Chief Executive Officer | Statement: [Virgin Orbit, Dan HartRole, Chief Executive Officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Dan HartRole Context triple: [Virgin Orbit, Dan HartRole, Chief Executive Officer]
-
A.
notableCastMember
Indicates that an entity is a member of the cast of another entity (such as a film, show, or production) and is considered particularly notable or significant in that role.
-
B.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
C.
Roger MullinParty
Indicates that there is a party affiliation relationship involving Roger Mullin.
-
D.
hallOfFameRole
Indicates the specific role, capacity, or category under which an entity is inducted into a hall of fame.
-
E.
notableWorkRole
Indicates that a person’s role or position is specifically associated with the creation, performance, or contribution to a notable work.
- 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.