Triple
T25643346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NS-16 mission |
E642889
|
entity |
| Predicate | organizationFounderOnBoard |
P47849
|
FINISHED |
| Object | Jeff Bezos |
—
|
NE NERFINISHED |
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: Jeff Bezos | Statement: [NS-16 mission, organizationFounderOnBoard, Jeff Bezos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizationFounderOnBoard Context triple: [NS-16 mission, organizationFounderOnBoard, Jeff Bezos]
-
A.
hasCoFounderRoleOf
Indicates that one entity holds the role or position of co-founder in relation to another entity, such as an organization or venture.
-
B.
currentFounder
chosen
Indicates that an entity is a present, active founder of another entity (such as an organization or company).
-
C.
companyFounderAssociated
Indicates that there is a notable connection or involvement between a company and an individual recognized as its founder.
-
D.
workIncludesRoleOfFounder
Indicates that a work involves or credits an entity in the specific role of founder.
-
E.
organizationFounded
Indicates that an organization was established or created at a specific point in time, often by a particular founder or founding entity.
- 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_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 21, 2026, 5:48 p.m.