Triple
T8055242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boca Chica, Texas |
E187981
|
entity |
| Predicate | spaceportRole |
P80788
|
FINISHED |
| Object | orbital launch site for SpaceX Starship |
—
|
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: orbital launch site for SpaceX Starship | Statement: [Boca Chica, Texas, spaceportRole, orbital launch site for SpaceX Starship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceportRole Context triple: [Boca Chica, Texas, spaceportRole, orbital launch site for SpaceX Starship]
-
A.
spaceportLocation
Indicates the place where a spaceport is situated or hosted.
-
B.
spaceportState
Indicates the operational or regulatory status currently assigned to a spaceport.
-
C.
operatesSpaceport
Indicates that one entity manages and runs the facilities and services of a spaceport for spacecraft operations.
-
D.
spaceSectorRole
Indicates the functional role or responsibility an entity holds within a specific space sector or domain.
-
E.
roleInSpaceX
Indicates that one entity holds or has held a specific role, position, or function within the organization SpaceX.
- 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_69ca82b2f68881908c50560697e210da |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3fa16804819094926ff2ff053c80 |
completed | March 31, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69cb049a1b9c8190811c396421ebf9c9 |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:25 p.m.