Triple
T34352004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scott L. Webster |
E881605
|
entity |
| Predicate | organizationFocusCoFounded |
P192243
|
FINISHED |
| Object | space launch vehicles |
—
|
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: space launch vehicles | Statement: [Scott L. Webster, organizationFocusCoFounded, space launch vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizationFocusCoFounded Context triple: [Scott L. Webster, organizationFocusCoFounded, space launch vehicles]
-
A.
companyFoundedFocus
Indicates that a company was founded with a particular primary focus, such as a specific industry, mission, or area of activity.
-
B.
organizationFocus
Indicates the primary area of activity, mission, or specialization that an organization is oriented toward or concentrated on.
-
C.
businessFoundedIn
Indicates that a business entity was established or came into existence in a specific location or time.
-
D.
foundedCompany
Indicates that an entity established or created a company, typically as its founder or co-founder.
-
E.
coFounderCompany
Indicates that a person is one of the founding members who jointly established a particular company.
- 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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69fd026757a081909911a59a78652709 |
completed | May 7, 2026, 9:21 p.m. |
Created at: May 1, 2026, 1:58 a.m.