Triple
T32849002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GSAT-9 |
E840189
|
entity |
| Predicate | programmeContext |
P180177
|
FINISHED |
| Object | South Asian Association for Regional Cooperation |
—
|
NE NERFINISHED |
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: South Asian Association for Regional Cooperation | Statement: [GSAT-9, programmeContext, South Asian Association for Regional Cooperation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programmeContext Context triple: [GSAT-9, programmeContext, South Asian Association for Regional Cooperation]
-
A.
programContext
Indicates the situational or environmental conditions (such as scope, settings, or surrounding code) within which a program or computational process is defined or executed.
-
B.
programmeStart
Indicates the point in time or event at which a programme begins or is initiated.
-
C.
programmeName
Indicates that an entity has or is identified by a specific programme’s name.
-
D.
premiereProgramContext
Indicates the contextual setting or circumstances (such as event, venue, or occasion) in which a program has its premiere.
-
E.
agencyProgramme
Indicates that an agency is responsible for, manages, or is associated with a particular programme.
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
| PDg | Predicate description generation | batch_69f73221eef88190bd8905e6e9f5a586 |
completed | May 3, 2026, 11:31 a.m. |
Created at: May 1, 2026, 1:17 a.m.