Triple
T25643331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NS-16 mission |
E642889
|
entity |
| Predicate | crewRoleOfJeffBezos |
P21967
|
FINISHED |
| Object | founder of Blue Origin |
—
|
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: founder of Blue Origin | Statement: [NS-16 mission, crewRoleOfJeffBezos, founder of Blue Origin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewRoleOfJeffBezos Context triple: [NS-16 mission, crewRoleOfJeffBezos, founder of Blue Origin]
-
A.
roleAtBerkshireHathaway
Indicates that an entity holds or held a specific role or position within Berkshire Hathaway.
-
B.
portfolioRole
Indicates the specific function, capacity, or position an entity holds within a portfolio or collection of assets.
-
C.
hasCrewRole
chosen
Indicates that an entity serves in a specific role or position within a crew associated with another entity.
-
D.
associatedCompanyNotableRole
Indicates that an entity has a notable role or position in a specified associated company.
-
E.
roleInSpaceX
Indicates that one entity holds or has held a specific role, position, or function within the organization SpaceX.
- F. None of above.
Provenance (3 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faa22e7c81908af7fe96952bebe0 |
completed | May 2, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:48 p.m.