Triple
T11146044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSLV-C11 |
E263671
|
entity |
| Predicate | launchCampaign |
P98039
|
FINISHED |
| Object | Chandrayaan-1 mission campaign |
—
|
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: Chandrayaan-1 mission campaign | Statement: [PSLV-C11, launchCampaign, Chandrayaan-1 mission campaign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchCampaign Context triple: [PSLV-C11, launchCampaign, Chandrayaan-1 mission campaign]
-
A.
plannedCampaign
Indicates that an entity has designed and scheduled a campaign to be executed in the future.
-
B.
promotionalCampaign
Indicates a relationship where one entity organizes or runs a coordinated set of marketing activities aimed at promoting another entity, product, or service.
-
C.
campaignType
Indicates the specific category or kind of campaign an entity is associated with or participates in.
-
D.
campaignStartContext
Indicates the circumstances, conditions, or triggering situation under which a campaign is initiated.
-
E.
ledCampaignIn
Indicates that an entity directed or was in charge of organizing and executing a campaign within a particular context or location.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e86e9ef48190b4df4b14319a954f |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75ce104908190b6cc31ef2f67846a |
completed | April 9, 2026, 8:01 a.m. |
| PDg | Predicate description generation | batch_69d7706116248190a87440bec3960884 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:28 p.m.