Triple
T10501845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SHAR |
E247689
|
entity |
| Predicate | isMajorLaunchSiteFor |
P37295
|
FINISHED |
| Object | commercial satellite launches by ISRO |
—
|
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: commercial satellite launches by ISRO | Statement: [SHAR, isMajorLaunchSiteFor, commercial satellite launches by ISRO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorLaunchSiteFor Context triple: [SHAR, isMajorLaunchSiteFor, commercial satellite launches by ISRO]
-
A.
hasMainLandingSite
Indicates that an entity has a primary or principal location where it arrives, lands, or makes contact.
-
B.
launchSites
Indicates locations from which an object, mission, or vehicle is launched or initiated.
-
C.
isPrimarySpaceportOf
chosen
Indicates that a given spaceport serves as the main or principal launch and operations facility for a specified region, organization, or celestial body.
-
D.
wasLandingSiteIn
Indicates that a specific landing event occurred at or within the location denoted by the related entity.
-
E.
isSatelliteSiteOf
Indicates that one site functions as a subsidiary, dependent, or secondary location associated with another primary or main site.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5099b797c8190a94803fa94eb6981 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:25 p.m.