Triple
T15468565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The World’s Premier Gateway to Space |
E372094
|
entity |
| Predicate | relatedToDomain |
P112931
|
FINISHED |
| Object | space launch operations |
—
|
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 operations | Statement: [The World’s Premier Gateway to Space, relatedToDomain, space launch operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToDomain Context triple: [The World’s Premier Gateway to Space, relatedToDomain, space launch operations]
-
A.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
B.
involvedDomain
chosen
Indicates that an entity participates in or is associated with a particular domain, field, or area of activity.
-
C.
relatedTLD
Indicates that one top-level domain (TLD) has an association or connection with another TLD, such as similarity, shared purpose, or contextual relevance.
-
D.
relatedToTerm
Indicates a general, non-specific relationship or association between one term and another.
-
E.
containsDomain
Indicates that one entity includes or encompasses a specific domain as part of its scope, structure, or area of applicability.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f69a31c81909a749247b6615d91 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:33 a.m.