Triple
T32256692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stargazer |
E824043
|
entity |
| Predicate | serviceEntryAsLaunchPlatform |
P72630
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Stargazer, serviceEntryAsLaunchPlatform, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceEntryAsLaunchPlatform Context triple: [Stargazer, serviceEntryAsLaunchPlatform, 1990s]
-
A.
serviceEntryWith
Indicates that one entity is associated with or accompanied by a particular service entry in a joint or linked context.
-
B.
servicePlatform
chosen
Indicates that one entity functions as a platform or environment through which services are provided, managed, or delivered to another entity.
-
C.
launchServiceEntry
Indicates initiating or starting the provision of a particular service or service instance.
-
D.
serviceEntryInROC
Indicates that a service entry is recorded or included in a Register of Companies (ROC) or similar official registry.
-
E.
launchServiceType
Indicates the type or category of launch service associated with an entity, such as the kind of launch operation or offering it provides.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 1, 2026, 12:41 a.m.