Triple
T32571402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GSAT-6 |
E832524
|
entity |
| Predicate | controlCentre |
P115681
|
FINISHED |
| Object | ISRO Master Control Facility |
—
|
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: ISRO Master Control Facility | Statement: [GSAT-6, controlCentre, ISRO Master Control Facility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlCentre Context triple: [GSAT-6, controlCentre, ISRO Master Control Facility]
-
A.
centralizesControlOf
Indicates that one entity consolidates and concentrates decision-making authority or governance power over another entity or set of entities.
-
B.
controlsSystem
chosen
Indicates that one entity has the authority or capability to direct, manage, or regulate the operation of a system.
-
C.
controlStand
Indicates that one entity manages, directs, or regulates the operation or behavior of another entity or system.
-
D.
controlApp
Indicates that one entity has the ability or authority to operate, manage, or direct the behavior of an application.
-
E.
centralCommand
Indicates that one entity serves as the primary controlling or coordinating authority over the operations, decisions, or activities of another entity or group.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: May 1, 2026, 1:03 a.m.