Triple
T1666885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starbase, Boca Chica, Texas |
E36031
|
entity |
| Predicate | primaryRoleForCompany |
P8439
|
FINISHED |
| Object | Starship development hub |
—
|
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: Starship development hub | Statement: [Starbase, Boca Chica, Texas, primaryRoleForCompany, Starship development hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRoleForCompany Context triple: [Starbase, Boca Chica, Texas, primaryRoleForCompany, Starship development hub]
-
A.
roleInIndustry
chosen
Indicates the specific function, position, or capacity an entity holds within a particular industry or sector.
-
B.
primaryPosition
Indicates the main role, job, or position an entity holds among potentially multiple positions.
-
C.
identificationRole
Indicates that an entity serves as an identifier or plays a role in uniquely distinguishing or recognizing another entity.
-
D.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
E.
roleInCompanyHistory
Indicates that an entity held a specific role or position during a particular period or event in a company's history.
- 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_69a8861286808190939afff3ce8ee31e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abc0e8d5648190915ff689c7ca42bc |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69a907d331748190963d4ab1a2741537 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.